-
Notifications
You must be signed in to change notification settings - Fork 259
Enable Private Nodes by default in GKE Node Pool #4682
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
Conversation
shubpal07
left a comment
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.
LGTM
|
/gemini review |
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.
Code Review
This pull request modifies the gke-node-pool module to enable private nodes by default, enhancing the security posture of GPU node pools by preventing the allocation of public IP addresses. The change involves updating the default value of the enable_private_nodes variable to true in both the README.md and variables.tf files. I have identified one issue related to the documentation in README.md that needs to be addressed.
ca61a8f to
6c7e817
Compare
|
We need to test for other machine families as well like A3 ultra which sets |
409fce0
into
GoogleCloudPlatform:develop
Disable public IP allocation by default in GKE node pools.
This is a potential security concern highlighted by the networking team. Fixed it by changing the default value of the
enable_private_nodesvariable in gke-node-pool module totrue.This change was tested by deploying sample blueprints, showing the VMs thus created to have no external IPs (only have internal IPs). A3M and G4 clusters were created successfully and tested before changing this default value.
Network connectivity tests were also performed to verify the deployed clusters were able to access the internet.