build(gatewayapi): bump bundled Envoy Gateway to v1.9.1 - #5296
Draft
electricjesus wants to merge 1 commit into
Draft
build(gatewayapi): bump bundled Envoy Gateway to v1.9.1#5296electricjesus wants to merge 1 commit into
electricjesus wants to merge 1 commit into
Conversation
Envoy Gateway v1.8.3 to v1.9.1, which moves the embedded helm chart's Gateway API bundle from v1.5.1 to v1.6.1 and the vendored sigs.k8s.io/gateway-api with it. v1.9.1 splits EnvoyGatewayKubernetesProvider into two embedded structs, EnvoyGatewayKubernetesInfrastructureConfiguration and EnvoyGatewayKubernetesConfiguration. Field access still promotes, so the render code is unchanged. Only a composite literal has to name the embedded struct, which is the one test change here. The JSON tags did not move, so parsing an EnvoyGateway config is unaffected. The v1.6.1 bundle adds one CRD, XBackend in gateway.networking.x-k8s.io. The suffix split in gateway_api.go already routes x-k8s.io into k8sCRDs, so it lands in the right bucket with no code change. Its operator RBAC lives in the calico repos, not here.
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
2 participants
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.
Description
Bumps the bundled Envoy Gateway from v1.8.3 to v1.9.1. That moves the embedded helm chart's Gateway API bundle from v1.5.1 to v1.6.1, and the vendored
sigs.k8s.io/gateway-apiwith it.Stacked on the Go 1.27.0 PR, which it needs: EG v1.9.1 declares
go 1.26.7and no go-build image exists below 1.27.0 that satisfies it.v1.9.1 splits
EnvoyGatewayKubernetesProviderinto two embedded structs,EnvoyGatewayKubernetesInfrastructureConfigurationandEnvoyGatewayKubernetesConfiguration. Field access still promotes, sogateway_api.gois unchanged. Only a composite literal has to name the embedded struct, which is the one test change here. The JSON tags did not move, so parsing anEnvoyGatewayconfig is unaffected.The v1.6.1 bundle adds one CRD,
XBackendingateway.networking.x-k8s.io. The name-suffix split ingateway_api.goalready routesx-k8s.iointok8sCRDs, so it lands in the right bucket with no code change. Its operator RBAC lives in the calico repos, not here.The v1.5.1 to v1.6.1 CRD change is additive:
TCPRouteandUDPRoutegainv1and keepv1alpha2, nothing loses a served version. So thesafe-upgradesValidatingAdmissionPolicy does not block an in-place upgrade, unlike v1.7 to v1.8.Test plan
make ut: 109 suites, all passed, 9m36s. That run includes the parent commit, so it covers the Go 1.27.0 move and the EG bump together.go build ./...andgo vet ./...clean.gateway-helm.tgzis the published v1.9.1 chart. Its sha256 matches the registry manifest digest, and itsgatewayapi-crds.yamlreadsbundle-version: v1.6.1,channel: experimental.Not covered: no live cluster. Two things want a real one before release. EG v1.9.1 moves EnvoyExtensionPolicy Lua from per-route to listener-level filters, which changes xDS filter names next to the coraza WASM filter. And
EndpointSliceIndexnow defaults on, which may raise controller memory.Release Note