Closed christiancadieux closed 2 weeks ago
what is your gatewayclass status ? do they got accepted ?
we have multi-tenancy deployment doc, can you check and see if it helps ?
This problem won't happen according to above doc.
I did follow the mult-tenant doc. I was expecting that since it's the gateway controller that created the envoy deployment in the first place, it should re-create it when it's deleted - but it failed with the mentioned error.
the status is:
status:
conditions:
- lastTransitionTime: "2024-06-19T22:09:45Z"
message: 'Invalid parametersRef: failed to list envoyproxies in namespace tenant1-eg:
unable to list: tenant1-eg because of unknown namespace for the cache'
observedGeneration: 1
reason: InvalidParameters
status: "False"
type: Accepted
I notices that this 'field is immutable' error goes away if I remove any labels from the envoyproxy spec. But with the pod labels, the proxy image is never updated and I see the 'field is immutable' error in the logs.
FAILS:
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: EnvoyProxy
metadata:
name: proxy-config-{{ .Values.tenant }}
namespace: {{ .Values.tenant }}-ns1
spec:
provider:
type: Kubernetes
kubernetes:
envoyDeployment:
pod:
labels:
tsf.io/tenant: {{ .Values.tenant }}
container:
image: {{ .Values.envoyproxyimage }}
but if I remove the pod section but leave the container.image - it all works.
ah this ties to https://github.com/envoyproxy/gateway/issues/1844, we need a way to opt in to force recreation
This issue has been automatically marked as stale because it has not had activity in the last 30 days.
Description:
saw this in the log
If I delete the deployment gateway and re-install - then the proxy deployment&pod comes-back:
this was a multi-namespace install:
Repro steps:
Environment:
Logs: