Remove cilium-config-path mount in cilium-agent container

[admun]

This PR removes cilium-config-path mount in the cilium-agent container.

This mount overwrites config generated by config initContainer. This caused CiliumNodeConfigs not working as expected.

This issue reported in #17269

[k8s-ci-robot]

Welcome @admun!

It looks like this is your first PR to kubernetes/kops 🎉. 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/kops 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 @admun. Thanks for your PR.

I'm waiting for a kubernetes 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.

[hakman]

/ok-to-test

[hakman]

/retest

[hakman]

/retest

[admun]

hi @hakman,

I think there are still a couple tests failed that seems relevance here. Anything I should be looking at to correct that?

Thanks for kick started this.

[rifelpet]

@admun please run ./hack/update-expected.sh and commit the resulting changes

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: admun / name: Edmond Hui (f1d81cb, 41f5d99)

[admun]

@rifelpet please see the commit.

Note, I made a mistake when pushing that commit to this PR with my work identify and easyCLA not happy about it....

I amended the commit after that and I think the issue should be cleared but the PR seems now become cncf-cla: no, how should I fix it?

nm, fixed the issue w/ some help.

[rifelpet]

/retest

[rifelpet]

/retest

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rifelpet

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

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

[k8s-ci-robot]

@admun: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kops-e2e-aws-upgrade-k130-ko130-to-klatest-kolatest-many-addons	f1d81cb	link	false	/test pull-kops-e2e-aws-upgrade-k130-ko130-to-klatest-kolatest-many-addons

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[admun]

@rifelpet Thank you so much for approving the PR!

One more question; Would this fix picks up by next release (1.31, I supposed) automatically?

Please let me know if there is a procedure I need to follow to ensure it lands in the next release.

[rifelpet]

I've cherrypicked this back to 1.32 and 1.31 so they should be included in the next round of patch releases