-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
None
-
3
-
False
-
None
-
False
-
-
-
OTA 256, OTA 257
Following up https://github.com/openshift/cincinnati-operator/pull/190#discussion_r1663190423
"All namespaces on the cluster" installs are no longer supported,
OSUS should work with namespaced permissions and thus the cluster level role/robindings should not be needed.
However, the attempt of migrating to role/rolebinding from clusterrole/clusterrolebinding failed
as the e2e job errored out
updateservices.updateservice.operator.openshift.io is forbidden: User "system:serviceaccount:openshift-updateservice:updateservice-operator" cannot list resource "updateservices" in API group "updateservice.operator.openshift.io" at the cluster scope
We should remove the API calls from OSUS that caused the error.
AC:
OSUS runs without any cluster-level permissions.
- is caused by
-
OCPBUGS-37091 There should be an error when osus instance not in same namespace with osus operator
- Closed
- is documented by
-
OTA-1317 Clearly document that OSUS operator and operands must run in a single namespace
- To Do
- links to