feat: support additional pod ranges and per-node-pool pod_range mapping#83
Merged
Conversation
maxsxu
approved these changes
May 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
Extend the GKE wrapper to support additional secondary pod IP ranges, so operators don't have to create overflow node pools manually via
gcloud(which causes terraform drift on every plan).Upstream module:
terraform-google-modules/kubernetes-enginev35.0.1 already exposesadditional_ip_range_pods(used to populateadditional_pod_ranges_config.pod_range_nameson the cluster) and a per-poolpod_range, but this wrapper doesn't surface either.Modifications
variables.tf:additional_pod_range_names(list(string), default[]) — names of additional secondary pod ranges to attach to the cluster.node_pool_pod_range_mapping(map(string), default{}) — per-pool override forpod_range, keyed by node-pool name.main.tf:additional_ip_range_pods = var.additional_pod_range_namestomodule.gke.default_node_pool_config.pod_rangeandfunc_pool_config.pod_rangenow look upvar.node_pool_pod_range_mapping[<pool-name>], falling back tovar.secondary_ip_range_pods(the primary).README.md: regenerated viaterraform-docs.Both new variables default to empty / no-op so existing consumers are unaffected.