Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Enable management of access to public/private API endpoints #1149
Enable management of access to public/private API endpoints #1149
Changes from all commits
0f59fb4
f71bd22
c3a43b2
f85e7de
a31bda9
a3f9eb0
06a51e8
69474a4
2659e95
01482c5
80c89ba
6cb7295
aa6c906
48a798c
d91b969
65a47cc
94e5618
7eec6d8
634d1e5
4a20215
d8a531b
c4b9260
5aac9b4
f147f3e
a084e7c
dc11d25
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I think it's acceptable to change the default for new clusters and enable private access, as currently private nodegroups have to go via NAT gateway to access the API...
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.
Should I then give the message that they'll need to update securitygroups/etc in order for clients within the VPC to communicate with the Kubernetes API whenever we create a cluster with these defaults?
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.
Need to discuss the UX of this. Seems like we need to say something about what users will need to do to make private access actually work. I can put the AWS URL that speaks to this in the output, but seems odd that the default configuration will flag immediately put this issue in front of them.