Added variables cilium_enable_host_firewall and cilium_policy_audit_mode for configmap/cilium-config

[ledroide]

What type of PR is this?

/kind feature

Special notes for your reviewer:

In order to enable (Cilium Host Firewall](https://docs.cilium.io/en/latest/security/host-firewall/) and the recommended PolicyAuditMode that prevents unwanted side effects during testing, we have added 2 variables to cilium role and to inventory (features are disabled by default) :

cilium_enable_host_firewall: false
cilium_policy_audit_mode: false

These features are then added in ConfigMap/cilium-config by cilium role - here set to "true" for the demo. Quotes and capitalized values in this configmap are required.

enable-host-firewall: "True"
policy-audit-mode: "False"

We have added related documentation in docs/cilium.md

Does this PR introduce a user-facing change?:

No facing change. Default settings are set to "false", so there is no difference to cilium behavior when keeping default values.

Add optional support for _Host Firewall_ and _PolicyAuditMode_ features in Cilium

[k8s-ci-robot]

Hi @ledroide. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ledroide]

The pipeline failed a week ago with error messages that do not have any relation with the changes of this PR.

How can I force these checks to run again ?

[ledroide]

Hello dear reviewers Arthur and Erik @MrFreezeex @ErikJiang.

Since I have pushed this PR a month ago, the check does not pass a test stage with error ci-not-authorized. It looks like I can't do anything about this error.

I had already tried the same changes in March, ref #10989 , and tried solve it by cancelling the first PR and open this one - unfortunately with no more success.

May you please test and approve this PR ?

[yankay]

/ok-to-test

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ledroide]

/remove-lifecycle stale

[ledroide]

Is it still ok to test ? When this test is it planned ?

[VannTen]

/approve

Can you squash your commits ? The last two fixes the first, so they should be one
(ok-to-test is merely to allow CI to run)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ledroide, VannTen

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [VannTen]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[VannTen]

/lgtm