chore: bump Envoy Gateway v1.4.3 -> v1.7.3 - #29
Closed
scotwells wants to merge 1 commit into
Closed
Conversation
Bump the Envoy Gateway control plane OCIRepository tag from v1.4.3 to v1.7.3 (chart and appVersion track the OCI tag via chartRef, so no other pin needs changing). Validated locally: kustomize build components/envoy-gateway-operator kustomize build components/envoy-gateway-operator/gateway-resources Both render cleanly; the gateway-resources EnvoyProxy/GatewayClass use only fields stable across 1.4 -> 1.7 (mergeGateways, provider.kubernetes, telemetry.metrics.prometheus). No CRD field removals affect these manifests. Motivation: align the test-infra control plane with the Envoy Gateway version targeted by network-services-operator so downstream Gateway/EPP fidelity experiments run against the production version. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Author
|
Superseded by #33 |
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
Bumps the Envoy Gateway control plane from v1.4.3 → v1.7.3 by updating the OCIRepository tag in
components/envoy-gateway-operator/oci-repository.yaml. The HelmRelease pulls chart + appVersion viachartRef, so the OCI tag is the only pin that needs to change.Why
network-services-operator (NSO) programs downstream Gateways and
EnvoyPatchPolicyresources whose xDS resource names (e.g.http-80,<ns>/<gw>/<listener>route configs,httproute/<ns>/<name>/rule/<idx>clusters) must match the Envoy Gateway version running in prod. We are standing up a controlled xDS-build-cost experiment on top of test-infra and need the control plane to be v1.7.3 to keep fidelity with production.Validation
Both render cleanly. The
gateway-resourcesEnvoyProxy/GatewayClass use only fields stable across 1.4 → 1.7 (mergeGateways,provider.kubernetes.envoyService/envoyDeployment,telemetry.metrics.prometheus); no CRD field removals affect these manifests. Full apply-time validation against live v1.7.3 CRDs is exercised by the consuming experiment (network-services-operator/experiments/xds-scaling).Risk
Low. Single tag change; flux reconciles the HelmRelease and rolls the
envoy-gatewaydeployment. Rollback is reverting the tag.🤖 Generated with Claude Code