-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow multi-CNI setups to set usesSecondaryIP #10828
Conversation
Welcome @ravens! |
Hi @ravens. 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 Once the patch is verified, the new status will be reflected by the 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. |
This option does prevent the install of incompatible networking options. The check you remove in this PR would allow specifying a user-managed CNI in addition to a kOps-managed CNI (or kubeet-like networking), which kOps cannot support. You can however set Could you elaborate more on your usecase for this? |
This case (cni + another cni) used to work with kops 1.17 - our use case on AWS is to use calico as main CNI and to use Multus to bring ENI to specific pods. Without the CNI option setup, Kubelet does not set up the --node-ip option and Kubelet starts to grab up all the IPs, creating duplicate internalIPs after a while. While I do see some CNI options being incompatible (i.e. Calico + Cilium), this particular one should not be marked as incompatible IMO. |
So it is actually I think maybe if you move this |
/cc @hakman |
@olemarkus thanks for the suggestion ! Indeed the focus is actually on the |
Thanks. Lets see if anyone else has any comments. If not, I'll merge in not too long. /assign |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olemarkus 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:
Approvers can indicate their approval by writing |
/ok-to-test |
…828-origin-release-1.19 Automated cherry pick of #10828: validation.go: remove checks on CNI
…828-origin-release-1.20 Automated cherry pick of #10828: validation.go: remove checks on CNI
This PR removes a previously introduced check on the CNI plugin presence.
The original PR #8617 seems to introduce some checks on the use of incompatible CNI plugins, but in fact the CNI plugin is used to set the
--node-ip
Kubelet option in case theuseSecondaryIP
flag is set to true. A Kops cluster operator should be able to declare that when using a CNI plugin like Calico for example.