Bug 1963041 - GitOps Operator can't be installed in ROSA cluster due namespaces used
Summary: GitOps Operator can't be installed in ROSA cluster due namespaces used
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Kevin Rizza
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-21 09:06 UTC by Nelson Lombo Paez
Modified: 2024-12-20 20:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-24 14:46:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Nelson Lombo Paez 2021-05-21 09:06:12 UTC
Description of problem:

The GitOps Operator can't be installed in ROSA cluster due the namespace used is `openshift-gitops` and is hardcoded here[1]:

~~~
var (
	port                       int32  = 8080
	portTLS                    int32  = 8443
	backendImage               string = "quay.io/redhat-developer/gitops-backend:v0.0.1"
	backendImageEnvName               = "BACKEND_IMAGE"
	serviceName                       = "cluster"
	insecureEnvVar                    = "INSECURE"
	insecureEnvVarValue               = "true"
	serviceNamespace                  = "openshift-gitops"
	depracatedServiceNamespace        = "openshift-pipelines-app-delivery"
	clusterVersionName                = "version"
)
~~~

Per ROSA policies [2] the namespaces `openshift-*` are considered as a core namespaces only for SRE use, so the customer can't use them.

**
[1] https://github.com/redhat-developer/gitops-operator/blob/a15f0c70541c9dcc7b9541c35e7e29bb9a880e3b/pkg/controller/gitopsservice/gitopsservice_controller.go#L49

[2] https://docs.openshift.com/rosa/rosa_policy/rosa-policy-process-security.html#rosa-policy-rh-access_rosa-policy-process-security
 
Version-Release number of selected component (if applicable):


How reproducible: Install the Operator and see that the namespace is not configurable


Actual results: The Operator is installed but the customer don't have privileges to work with it



Additional info:


Note You need to log in before you can comment on or make changes to this bug.