-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
False
-
-
False
-
-
-
0
-
Low
USER PROBLEM
What is the user experiencing as a result of the bug? Include steps to reproduce.
- When generating network policies for deployments in different namespaces with the RHACS portal, by using the network graph, the generated policies do not add the namespace.metadata.stackrox.io/name label to the namespaces.
- Instead, the generated policies use the existing kubernetes.io/metadata.name label.
- However, the documentation (https://docs.openshift.com/acs/4.6/operating/manage-network-policies.html#policy-generation-strategy-ng20_manage-network-policies) says: "For deployments in different namespaces, this rule uses a namespace selector. To make this possible, RHACS automatically adds a label, namespace.metadata.stackrox.io/name, to each namespace."
CONDITIONS
What conditions need to exist for a user to be affected? Is it everyone? Is it only those with a specific integration? Is it specific to someone with particular database content? etc.
- Everyone
ROOT CAUSE
What is the root cause of the bug?
- The documentation seems incorrect or outdated.
FIX
How was the bug fixed (this is more important if a workaround was implemented rather than an actual fix)?
- I ignored the sentence from the documentation that indicate that namespaces get a new label.
- Maybe the doc should say: "For deployments in different namespaces, this rule uses a namespace selector. The rule uses the kubernetes.io/metadata.name label that Kubernetes sets on all namespaces."