Add configuration to create cilium CNI plugin file when cilium>=1.14.0

[cleman95]

What type of PR is this?
/kind bug

What this PR does / why we need it:
Cilium 1.14.0 is no longer creating its cni plugin file under /etc/cni/net.d by default. To fix this we must add the write-cni-conf-when-ready key inside the cilium-config configMap .

This will also fix the fact that the keys cilium_cni_exclusive and cilium_cni_log_file are no longer used when deploying cilium 1.14.0 .

Which issue(s) this PR fixes:
Fixes #10887

Special notes for your reviewer:
/sig network

This change was introduce in Cilium 1.14 with this commit .

They removed the script (cni-install.sh) that was in charge of creating the cni-plugin file.

Does this PR introduce a user-facing change?:

NONE

[linux-foundation-easycla]

• ✅login: cleman95 / (232c5b9)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

Welcome @cleman95!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @cleman95. 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/test-infra repository.

[yankay]

/ok-to-test

[cyclinder]

This will also fix the fact that the keys cilium_cni_exclusive and cilium_cni_log_file are no longer used when deploying cilium 1.14.0 .

These only be used when cilium version < 1.14.0, right?

[cleman95]

No these are still needed when cilium version >= 1.14.0 . They deleted the cni-install.sh used in the postStart hook which was taking these keys as args but now they need to be passed via the ConfigMap.

[cyclinder]

got it, thanks for the expiation！

[cyclinder]

thanks for the fix!

/lgtm

[cleman95]

/assign @floryut

[yankay]

Thanks @cleman95
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cleman95, cyclinder, yankay

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 [yankay]

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

[yankay]

HI @cleman95

A fix a PR should be merged into the master branch first and then cherry-pick to the release branch :-)

Would you please help to create a patch for the PR and merge it into the master branch?