Previously, the operator would process dopplersecret resources in any namespace, effectively allowing token secrets to be read and managed secrets to be updated in any namespace in the cluster. This pattern is unintuitive and inconsistent with the Kubernetes RBAC rules. This PR requires all dopplersecret resources to be in the same namespace as the operator deployment (doppler-operator-system by default) in order to be reconciled.
Previously, the operator would process
dopplersecret
resources in any namespace, effectively allowing token secrets to be read and managed secrets to be updated in any namespace in the cluster. This pattern is unintuitive and inconsistent with the Kubernetes RBAC rules. This PR requires alldopplersecret
resources to be in the same namespace as the operator deployment (doppler-operator-system
by default) in order to be reconciled.Closes #21