-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Add option to skip endpoint creation completely #4457
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -60,6 +60,21 @@ privateCluster: | |
|
|
||
| The endpoints supported in `additionalEndpointServices` are `autoscaling`, `cloudformation` and `logs`. | ||
|
|
||
| ### Skipping endpoint creations | ||
|
|
||
| If a VPC has already been created with the necessary AWS endpoints set up and linked to the subnets described in the EKS documentation, | ||
| `eksctl` can skip creating them by providing the option `skipEndpointCreation` like this: | ||
|
|
||
| ```yaml | ||
| privateCluster: | ||
| enabled: true | ||
| skipEndpointCreation: true | ||
|
Comment on lines
+69
to
+71
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. is having it under
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. VPCEndpoints are only relevant in private clusters.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. cool! |
||
| ``` | ||
|
|
||
| _Note_: this setting cannot be used together with `additionalEndpointServices`. It will skip all endpoint creation. Also, this setting is | ||
| only recommended if the endpoint <-> subnet topology is correctly set up. I.e.: subnet ids are correct, `vpce` routing is set up with prefix addresses, | ||
| all the necessary EKS endpoints are created and linked to the provided VPC. `eksctl` will not alter any of these resources. | ||
|
|
||
| ## Nodegroups | ||
| Only private nodegroups (both managed and self-managed) are supported in a fully-private cluster because the cluster's VPC is created without | ||
| any public subnets. The `privateNetworking` field (`nodeGroup[*].privateNetworking` and `managedNodeGroup[*].privateNetworking`) must be | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.