-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.10
-
Moderate
-
None
-
Unspecified
-
If docs needed, set a value
-
Description of problem:
TALM pod is created under the same namespace as subscription and csv (openshift-operators). But it should have been deployed under its dedicated namespace.
Version-Release number of selected component (if applicable):
4.10
How reproducible:
100%
Steps to Reproduce:
1. Deploy TALM with subscription namespace set to openshift-operators
2. Check TALM pods after deployed
3.
Actual results:
TALM pods are created under openshfit-operators namespace
Expected results:
TALM deployment/pods should be created under its dedicated namespace that should not be changeable by user. (e.g., openshift-talm)
Additional info:
openshift-gitops operator works as expected. i.e., its subscription is created under openshift-operators namespace, but the deployments/servies/pods are always created under openshift-gitops namespace, and the namespace is auto created as well.
https://docs.openshift.com/container-platform/4.9/cicd/gitops/installing-openshift-gitops.html