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

Allow setting enable_private_nodes in GKE nodepool pod range #1808

Merged
merged 1 commit into from
Oct 24, 2023

Conversation

ludoo
Copy link
Collaborator

@ludoo ludoo commented Oct 24, 2023

Fixes #1807

@ludoo ludoo requested review from juliocc and wiktorn October 24, 2023 17:11
@ludoo ludoo changed the title allow setting enable_private_nodes in gke nodepool pod range Allow setting enable_private_nodes in GKE nodepool pod range Oct 24, 2023
@ludoo ludoo enabled auto-merge (squash) October 24, 2023 17:25
@ludoo ludoo merged commit 1b3a4d6 into master Oct 24, 2023
13 checks passed
@ludoo ludoo deleted the ludo/gke-nodepool-private-nodes branch October 24, 2023 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[bug] For GKE nodepool in a private cluster, when specify pod_range we need to set enable_private_nodes
2 participants