-
Story
-
Resolution: Won't Do
-
Undefined
-
None
-
None
-
None
-
None
-
False
-
-
False
-
3
-
None
-
None
-
None
As an admin, I'd like any of the catalog operators to install in `openshift-*` namespaces without additional overhead so that I may focus on higher-value tasks.
Context: This ticket depends on OLM-2669. Rather than generating an event when installing an operator in an openshift-* namespace, now we add the `security.openshift.io/scc.podSecurityLabelSync=true` label to the namespace.
A/C
- openshift-* namespaces with operator installations get labeled with `security.openshift.io/scc.podSecurityLabelSync=true`
- openshift-* namespace that already have the `security.openshift.io/scc.podSecurityLabelSync` label, whether set to true or false, are ignored