-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
RFE to not create openshift-gitops namespace if DISABLE_DEFAULT_ARGOCD_INSTANCE is used
Feature Overview
- With the Subscription options set
- ARGOCD_CLUSTER_CONFIG_NAMESPACES
- DISABLE_DEFAULT_ARGOCD_INSTANCE
the namespace `openshift-gitops` is still created for the UI plugin and the Cluster service. In restricted clusters that need to stay `compliant` this creates a violation to various (mostly German) rules and regulations.
- Not creating the UI/Cluster resource as well as not creating the namespace is the aim of this RFE.
- It is understood that those features (UI/Cluster) are than not use-able.
Business Goal/Objective
- Compliance deployments of OpenShift-Gitops provided by Red Hat in custom/tailored way for multi tenancy and small ArgoCD deployments.
- with Compliance violations on the table the removal of these resources which need to be done currently manually (and by a different Team) should be in the Operator as soon as possible.
- All German BSI/PCI-DSS4.0 affected customers are suffering.
Goals
- When specifying to `DISABLE_DEFAULT_ARGOCD_INSTANCE` all cluster wide resource (UI Plugin, ArgoCluster CR/service, openshift-gitops namespace) shall be not created.