Arko Dasgupta

hey I know @chauhanshubham was looking into a similar test for control plane upgrades which would invariably also upgrade envoy proxy, should we just collapse those two e2e tests into...

hey @guydc I was hoping we could have some test for hitless upgrade in v1.0, with caveats, that can hopefully we removed over time post GA do agree, we can...

this should be fixed with #2633, keeping this open so that it can be validated with a e2e

fixed with https://github.com/envoyproxy/gateway/pull/2862

@zesiar0 can you comment here, so we can assign this to you ?

@zesiar0 still planning on working on this ? (this issue is a release blocker for v1.0.0 releasing next week), if not, I can pick this one up, thanks !

ptal @monsur

2 options here * change it to `IfNotPresent` only for pinned releases * set the default to `IfNotPresent` and change it to `Always` for `v0.0.0-latest` ptal @envoyproxy/gateway-maintainers

related https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#enable-cors

From a correctness perspective [envoyproxy/gateway:v1.0.0-rc.1](https://hub.docker.com/layers/envoyproxy/gateway/v1.0.0-rc.1/images/sha256-ef041655bb9cb9327479f6c3aa46f08050531f729986fdb653583dbd8944a5de?context=explore) is the same as [envoyproxy/gateway-dev:7d48480](https://hub.docker.com/layers/envoyproxy/gateway-dev/7d48480/images/sha256-ef041655bb9cb9327479f6c3aa46f08050531f729986fdb653583dbd8944a5de?context=explore) but this is an extra image dependency that should not be required When releasing a image, we retag a image...