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 dependents can only specify cluster-scoped owners. In v1.20+, if a cluster-scoped dependent specifies a namespaced kind as an owner, it is treated as having an unresolvable owner reference, and is not able to be garbage collected.
Thus deleting the monitoring-stack will not delete the cluster-roles it creates. A workaround for it is to use finalizers on monitoring-stack and get the reconciler to delete clusterscoped resources before removing the finalizer.
The text was updated successfully, but these errors were encountered:
OwnerReferences do not work across namespaces and it equally applies to cluster-scoped resources
See: https://kubernetes.io/docs/concepts/overview/working-with-objects/owners-dependents/#owner-references-in-object-specifications
Thus deleting the monitoring-stack will not delete the cluster-roles it creates. A workaround for it is to use finalizers on monitoring-stack and get the reconciler to delete clusterscoped resources before removing the finalizer.
The text was updated successfully, but these errors were encountered: