-
Notifications
You must be signed in to change notification settings - Fork 1k
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
feat: Add new configuration for service CIDR to enable Windows bootstrapping #4625
Conversation
✅ Deploy Preview for karpenter-docs-prod canceled.
|
6fb961b
to
02ee419
Compare
02ee419
to
51d1de9
Compare
51d1de9
to
5ae7396
Compare
@@ -172,6 +172,8 @@ settings: | |||
# -- Cluster endpoint. If not set, will be discovered during startup (EKS only) | |||
clusterEndpoint: "" | |||
# -- The default instance profile to use when launching nodes | |||
clusterServiceIpv4Cidr: "" |
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.
Is it possible to discover this value from the cluster rather than specifying it within the karpenter-global-settings
?
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.
Yes its possible. Currently it is discovering the value from the EKS cluster if the value is not specified. Perhaps we can skip having it in karpenter-global-settings
altogether and rely on automatically fetching it?
Discussed offline with @tzifudzi: Looking into some options for users to specify this from environment variables in the |
Closing this PR in favour of a different approach |
Fixes #4088
Description
TODO
How was this change tested?
TODO
Does this change impact docs?
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.