fix: allocate Envoy Gateway/Grafana NodePorts dynamically - #35
Draft
scotwells wants to merge 1 commit into
Draft
Conversation
Fixed nodePort/hostPort values (30443, 30080, 30000) prevented running more than one test-infra cluster on the same Docker host, since kind's extraPortMappings bind to fixed host ports and Docker refuses to bind the same host port twice. Drop the extraPortMappings from cluster/kind-config.yaml and the nodePort overrides from the EnvoyProxy/Grafana Service patches so Kubernetes assigns an ephemeral NodePort per cluster instead. Add gateway-port-forward/grafana-port-forward tasks as the recommended way to reach these services now that the port isn't fixed.
scotwells
marked this pull request as draft
July 23, 2026 02:31
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
1 participant
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.
Summary
test-infrakind cluster on the same Docker host — Docker refuses to bind the same host port twice, socluster-upwith a secondCLUSTER_NAMEwould fail on port conflicts.extraPortMappingsfromcluster/kind-config.yamland thenodePortoverrides from theEnvoyProxy/GrafanaServicepatches. Kubernetes now allocates an ephemeral NodePort per cluster instead.task gateway-port-forward/task grafana-port-forwardas the recommended way to reach these services now that the port isn't fixed, and updates docs/messaging accordingly.Motivation
Needed for dns-operator's new local test environment, which stands up two concurrent kind clusters (control + edge) on the same host to exercise PowerDNS Lightningstream edge federation end-to-end.
Test plan
kustomize build components/envoy-gateway-operator/gateway-resourcesbuilds cleanly with nonodePortfieldtask cluster-up CLUSTER_NAME=aandtask cluster-up CLUSTER_NAME=bsucceed concurrently on the same hosttask gateway-port-forward/task grafana-port-forwardreach the expected services