-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
cluster-compare run against OCP 4.18 adding a few defaults that are not captured and shown as diff:
Cluster CR: v1_Namespace_openshift-nmstate Reference File: required/networking/NMStateNS.yaml Description: https://docs.openshift.com/container-platform/4.18/scalability_and_performance/telco_ref_design_specs/core/telco-core-ref-design-components.html#telco-core-nmstate-operator_core-ref-design-components Diff Output: diff -u -N /tmp/MERGED-226310527/v1_namespace_openshift-nmstate /tmp/LIVE-4277288633/v1_namespace_openshift-nmstate --- /tmp/MERGED-226310527/v1_namespace_openshift-nmstate 2025-07-14 12:52:43.169295957 +0000 +++ /tmp/LIVE-4277288633/v1_namespace_openshift-nmstate 2025-07-14 12:52:43.169295957 +0000 @@ -1,4 +1,7 @@ apiVersion: v1 kind: Namespace metadata: + labels: + name: openshift-nmstate + openshift.io/cluster-monitoring: "true" name: openshift-nmstate
Version-Release number of selected component (if applicable):
oc cluster-compare --version cluster-compare version v4.19.0 (2025-06-16 19:41:48+00:00)
How reproducible:
Always when the corresponding CR is applied as part of the rds-core cluster compliance step.
Steps to Reproduce:
1. oc apply -f required/networking/NMStateNS.yaml
2. oc cluster-compare -r metadata.yaml
Actual results:
Expected results:
No diff, or defaults should be captured by cluster-compare.
Additional info: