-
Notifications
You must be signed in to change notification settings - Fork 360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes to Gateway infrastructure labels fail to propagate to the service and pods #3666
Comments
seeing |
I don't think it's the same but it's related. for example with Services, it's important to update the labels of the service and not delete/re-create the service since re-creating would assign a new external-IP to the service, which is not good. |
i'll bring this up in the community meeting tomorrow, the issue is the same - should Envoy Gateway recreate resources when it hits this specific error |
no need to re-create resources to update labels. It is possible to update labels with PATCH:
or pod:
|
-1 to recreation. As stated, there are many possible side effects, including IP change, disruption to traffic, etc. |
hey @sanposhiho can you help with this one if you have a cycle ? |
/assign I'll take a look. |
Had a bit of time checking this issue. According to the provided logs, looks like it doesn't get a conflict at labels, but get conflicted at deployment's selector. So, I believe this issue is the same as #1818, as @arkodg mentioned first. |
closed in favour of #3995 |
Description:
Changes to Gateway infrastructure labels do not propagate to the service and pods
Repro steps:
Note:
maybe related to other 'immutable' bugs like #1818
Deleting the Gateway does delete the envoy-proxy deployment
Environment:
Gateway
PODS
Logs:
the logs when the gateway labels are updated:
The text was updated successfully, but these errors were encountered: