Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

tzifudzi
Copy link
Contributor

Fixes #4088

Description
TODO

How was this change tested?
TODO

Does this change impact docs?

  • Yes, PR includes docs updates

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@netlify
Copy link

netlify bot commented Sep 14, 2023

Deploy Preview for karpenter-docs-prod canceled.

Name Link
🔨 Latest commit 5ae7396
🔍 Latest deploy log https://app.netlify.com/sites/karpenter-docs-prod/deploys/6502650435b8df000878fff3

tzifudzi added a commit to tzifudzi/karpenter that referenced this pull request Sep 14, 2023
@tzifudzi tzifudzi force-pushed the feat/windows-service-cidr branch from 6fb961b to 02ee419 Compare September 14, 2023 00:23
@tzifudzi tzifudzi changed the title feat: Add new service Ipv4 Cidr to enable Windows bootstrapping feat: Add new configuration for service CIDR to enable Windows bootstrapping Sep 14, 2023
tzifudzi added a commit to tzifudzi/karpenter that referenced this pull request Sep 14, 2023
@tzifudzi tzifudzi force-pushed the feat/windows-service-cidr branch from 02ee419 to 51d1de9 Compare September 14, 2023 00:37
@tzifudzi tzifudzi force-pushed the feat/windows-service-cidr branch from 51d1de9 to 5ae7396 Compare September 14, 2023 01:42
@@ -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: ""
Copy link
Contributor

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?

Copy link
Contributor Author

@tzifudzi tzifudzi Sep 14, 2023

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?

@jonathan-innis
Copy link
Contributor

jonathan-innis commented Sep 15, 2023

Discussed offline with @tzifudzi: Looking into some options for users to specify this from environment variables in the userData or to get this info directly from the APIServer. We want to avoid users having to specify this at a global level in the karpenter-global-settings

@tzifudzi
Copy link
Contributor Author

Closing this PR in favour of a different approach

@tzifudzi tzifudzi closed this Sep 20, 2023
@tzifudzi tzifudzi deleted the feat/windows-service-cidr branch October 8, 2023 22:24
@aws aws locked and limited conversation to collaborators Oct 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Automatically include ServiceCIDR as an argument to Windows nodes bootstrap
2 participants