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
Cluster scoped resources like ControlPlane's ClusterRole and ClusterRoleBinding incorrectly use namespaced resources - ControlPlanes - as their owner which create OwnerRefInvalidNamespace events:
Unfortunately, we need to have a controlplane reference on the controlplane-owned cluster-wide resources, and the ownerRef is the easiest one. If we want to remove it, we'll need to think about a different mechanism, such as an annotation on the cluster-wide resource that points to the controlplane.
If we want to remove it, we'll need to think about a different mechanism, such as an annotation on the cluster-wide resource that points to the controlplane.
... or even a label which would make listing more efficient.
While owner ref does represent the actual relationship it's disallowed hence my proposal would be to use the labels for this.
Current Behavior
Cluster scoped resources like
ControlPlane
'sClusterRole
andClusterRoleBinding
incorrectly use namespaced resources -ControlPlane
s - as their owner which createOwnerRefInvalidNamespace
events:Expected Behavior
Cluster scoped resources shouldn't set namespaced resources as their owners.
Steps To Reproduce
ControlPlane
being deployed e.g. https://github.com/Kong/gateway-operator/blob/4e516dbbbc02d86f9601c7aed6182fc865b19cde/config/samples/gateway-with-gatewayconfiguration.yamlOperator Version
4e516db
Related materials
https://kubernetes.io/docs/concepts/overview/working-with-objects/owners-dependents/
The text was updated successfully, but these errors were encountered: