-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Add Kubernetes IPAM mode #10407
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
Add Kubernetes IPAM mode #10407
Conversation
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.
Also, shouldn't we add something in the upgrade guide with regarding the default value of the ipam
option?
Does anything change for the user? This should be invisible except for the help text and the logfile which now documents that the legacy hostscope is in use. |
5e4726f
to
156324c
Compare
test-me-please |
156324c
to
e7f479e
Compare
In order to test different IPAM modes easily in the future, remove direct access to option.Config in order to allow mocking the configuration interface. Signed-off-by: Thomas Graf <thomas@cilium.io>
Explicitly set the current default IPAM mode in the viper option. This enables introduction of a better default. Signed-off-by: Thomas Graf <thomas@cilium.io>
This documents an IPAM mode which was already supported and widely used but difficult to discover. The new "kubernete" IPAM mode requires the PodCIDR for all enabled address families to be provided via the k8s Node resource and then uses the standard hostscope allocator. Signed-off-by: Thomas Graf <thomas@cilium.io>
e7f479e
to
e79a9e4
Compare
test-me-please |
This was introduced by #10407 and makes the spell checker fail. Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
This was introduced by #10407 and makes the spell checker fail. Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
This change is