-
Epic
-
Resolution: Won't Do
-
Major
-
None
-
None
-
Enable users with restricted access to use kam
-
False
-
False
-
To Do
-
SECFLOWOTL-56 - Facilitate adopting CI/CD & GitOps
-
0% To Do, 0% In Progress, 100% Done
-
Undefined
-
-
Problem:
Many application teams do not have cluster-admin access to their OpenShift clusters and they operate within a constrained shared environment managed by the platform team. In some cases, they do not have access to create namespaces either and they should request a namespace to be created for them.
Customers using OpenShift Dedicated do not have cluster-admin access to the OSD clusters either and rather given a "dedicated-admin" role which is limited to certain administrative tasks.
Goal:
Enable application teams that do NOT have cluster-admin access to the OpenShift cluster to use kam to bootstrap a GitOps process across the namespaces they have access to.
Acceptance criteria:
- Users with standard namespace privileges (non cluster-admin) can use kam to configure a GitOps process across namespaces they have access to.
- Users can use existing namespaces that are created for them with kam