-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
Improvement
-
False
-
None
-
False
-
Not Selected
-
-
-
1. Proposed title of this feature request
Installing Openshift Logging Operator on Different Namesapce
2. What is the nature and description of the request?
A customer wants to deploy the Openshift Operator/Loki Operator on different (non-default) namespace, not on the default `openshift-operators-redhat namespce`.
3. Why does the customer need this? (List the business requirements here)
As per the customer, it would be better practice if deploying Openshift Operators like Openshift Logging and Loki Operator on non-default namespaces.
4. List any affected packages or components.
When they tried deploying Loki Operator on different namespace, as expected they encountered the following errors:
Error: Get "https://172.24.8.23:8443/metrics": tls: failed to verify certificate: x509: certificate is valid for loki-operator-controller-manager-metrics-service.openshift-loki-operator.svc, loki-operator-controller-manager-metrics-service.openshift-loki-operator.svc.cluster.local, not loki-operator-controller-manager-metrics-service.openshift-operators-redhat.svc