-
Bug
-
Resolution: Done
-
Minor
-
netobserv-1.7, netobserv-1.7-candidate
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
NetObserv - Sprint 260, NetObserv - Sprint 261
-
None
-
None
-
Description of problem:
When deploying netobserv network policy, the ingress rule for allowing openshift-console ingress connection is listed twice (once with a port restriction, another without).
Steps to Reproduce:
1. Install netobserv + FlowCollector with networkPolicy.enable=true and additional namespace left unset 2. check policy (oc get netpol netobserv -oyaml) 3.
Actual results:
ingress:
- from:
- podSelector: {}
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: netobserv-privileged
- from:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: openshift-console
ports:
- port: 9001
protocol: TCP
- from:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: openshift-user-workload-monitoring
- from:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: openshift-console
- from:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: openshift-monitoring
Expected results:
no duplicate section for openshift-console