-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
support disabling default cni #530
support disabling default cni #530
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder 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 |
// this step might be skipped, but is next after init | ||
if !cfg.Networking.DisableDefaultCNI { | ||
actionsToRun = append(actionsToRun, | ||
installcni.NewAction(), // install CNI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we could alternatively guard against this inside the action, I'm not sure this detail is important currently though as both are wholly internal to kind and should have roughly the same effect, but that might be a better refactor in the future.
/lgtm |
fixes #205 (though perhaps we need to follow up with docs 🙃 )
With this feature, users can skip the CNI installation and instead install their own CNI using the usual mechanisms (
kubectl apply -f my-cni-manifest.yaml ...
). This is an advanced use case and not strongly supported, but should be available. It seems a number of projects have found installing / testing their own CNI useful, and this makes it easier to do without poking at kind's internals 😉