-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.21
-
Quality / Stability / Reliability
-
False
-
-
2
-
None
-
None
-
None
-
Rejected
-
OAPE Sprint 279
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The must-gather-operator creates Job pods in the operator namespace instead of the MustGather Custom Resource namespace. When a MustGather CR is created in a custom namespace, the corresponding Job pod should be created in the same namespace, but it's currently being created in the must-gather-operator namespace.
Version-Release number of selected component (if applicable):
4.21, 4.20
How reproducible:
Always
Steps to Reproduce:
# Create a custom namespace: {{kubectl create namespace test-mustgather}}
# Create a MustGather CR in the custom namespace: {{kubectl apply -n test-mustgather -f mustgather-cr.yaml}}
# Observe where the Job pod is created: {{kubectl get jobs --all-namespaces}}
Actual results:
The Job pod is created in the must-gather-operator namespace instead of the test-mustgather namespace where the MustGather CR was created.
Expected results:
The Job pod should be created in the same namespace as the MustGather CR (test-mustgather namespace in this example).
Additional info:
This affects namespace isolation and may cause issues with RBAC and resource management.
- blocks
-
OCPBUGS-63748 [must-gather-operator] Job pod is not created in the MustGather CR namespace
-
- MODIFIED
-
- impacts account
-
MG-126 Verify OCPBUGS-63705: fix Job namespace per reconcile(d) instance.Namespace #303
-
- To Do
-
- is cloned by
-
OCPBUGS-63748 [must-gather-operator] Job pod is not created in the MustGather CR namespace
-
- MODIFIED
-
- is related to
-
OCPBUGS-63243 [must-gather-operator] hard-coded dependency on namespace causes deployment failure and inability to correctly configure metrics
-
- Verified
-
- links to