When a RolloutManager is deleted, all of the resources that were owned by the RolloutManager should also be deleted.
However, since ClusterRole/ClusterRoleBinding are cluster-scoped resources, they cannot be owned by a namespace-scoped resource like RolloutManager. Thus, CR/CRB do not have an owner, and thus, when the RM is deleted, the CR/CRB will not be garbage collected. The CR/CRB will continue on the cluster indefinitely.
We should update the logic we use to ensure that when we detect that an RM no longer exists, that we delete the corresponding CR/CRB.
When a RolloutManager is deleted, all of the resources that were owned by the RolloutManager should also be deleted.
However, since ClusterRole/ClusterRoleBinding are cluster-scoped resources, they cannot be owned by a namespace-scoped resource like RolloutManager. Thus, CR/CRB do not have an owner, and thus, when the RM is deleted, the CR/CRB will not be garbage collected. The CR/CRB will continue on the cluster indefinitely.
We should update the logic we use to ensure that when we detect that an RM no longer exists, that we delete the corresponding CR/CRB.