You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I found when working on https://github.com/Kong/gateway-operator/pull/1442, it seems possible currently for us to update Gateway resources which we don't control, as we manage cleanup and finalizers for Gateway resources prior to verifying support of those resources via GatewayClass.
Expected Behavior
We should not be updating resources we don't control, as this may collide with other Gateway implementations on the cluster.
Steps To Reproduce
deploy the KGO
deploy any other Gateway implementation
create a Gateway for the other implementation, see that we are adding and removing finalizers to it
Current Behavior
As I found when working on https://github.com/Kong/gateway-operator/pull/1442, it seems possible currently for us to update
Gateway
resources which we don't control, as we manage cleanup and finalizers forGateway
resources prior to verifying support of those resources viaGatewayClass
.Expected Behavior
We should not be updating resources we don't control, as this may collide with other
Gateway
implementations on the cluster.Steps To Reproduce
Gateway
for the other implementation, see that we are adding and removing finalizers to itOperator Version
c73b6aa
kubectl version
v1.27.10
The text was updated successfully, but these errors were encountered: