Repository navigation
feat: support loadBalancerIP on the Service - #159
Merged
Merged
Conversation
A LoadBalancer Service could not be pinned to a pre-reserved IP. On GKE without GKE subsetting, spec.loadBalancerIP is the only way to give an internal load balancer a static address; the annotation alternative requires subsetting. Add an optional service.loadBalancerIP value, rendered only when set, and a test values file covering it.
meskill
approved these changes
Nov 3, 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.
Adds an optional
service.loadBalancerIPso a LoadBalancer Service can be pinned to a pre-reserved IP.Rendered only when set. No change for anyone not using it: the default render has no
loadBalancerIP.Adds
test/values-load-balancer-ip.yaml;test/test.shpasses (lint, kubeconform across all values files, existing assertions).