-
Notifications
You must be signed in to change notification settings - Fork 411
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
Set ownerReference on gateway Deployment #3051
Comments
Makes sense, similar to #1706
|
+1 |
rethinking, this work may be a little bit more involved, we lose exact info of the Line 39 in 3d51933
|
same to |
merged gateways should ref the GatewayClass |
not the prettiest and slightly fragile, but the easiest solution is to update the ownerReference based on the owning labels created gateway/internal/gatewayapi/helpers.go Line 230 in 8a01dd6
|
this cannot be implemented with the default deployment configuration because ownerReferences dont have cross namespace support, the |
this can only work for the mergeGateways case where the owner is a cluster scoped resource like |
@arkodg, I tried adding the
|
Description:
Would be cool to see
Deployment
created forGateway
to haveownerReference
forGateway
.This allows following chain and for example makes ArgoCD show the deployment where
Gateway
is created in ArgoCD application.The text was updated successfully, but these errors were encountered: