Skip to content

Commit 8994922

Browse files
gwynnemonahankalexand-rh
authored andcommitted
OSDOCS-16177 [NETOBSERV] Update network policy content
1 parent d2620f9 commit 8994922

File tree

2 files changed

+9
-8
lines changed

2 files changed

+9
-8
lines changed

modules/network-observability-deploy-network-policy.adoc

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,14 @@
55

66
:_mod-docs-content-type: PROCEDURE
77
[id="network-observability-deploy-network-policy_{context}"]
8-
= Configuring an ingress network policy by using the FlowCollector custom resource
8+
= Configuring network policy by using the FlowCollector custom resource
99

10-
You can configure the `FlowCollector` custom resource (CR) to deploy an ingress network policy for network observability by setting the `spec.NetworkPolicy.enable` specification to `true`. By default, the specification is `false`.
10+
[role="_abstract"]
11+
You can set up ingress and egress network policies to control pod traffic. This enhances security and collects only the network flow data you need. This reduces noise, supports compliance, and improves visibility into network communication.
1112

12-
If you have installed Loki, Kafka or any exporter in a different namespace that also has a network policy, you must ensure that the Network Observability components can communicate with them. Consider the following about your setup:
13+
You can configure the `FlowCollector` custom resource (CR) to deploy an egress and ingress network policy for network observability. By default, the `spec.NetworkPolicy.enable` specification is set to `true`.
14+
15+
If you have installed Loki, Kafka or any exporter in a different namespace that also has a network policy, you must ensure that the network observability components can communicate with them. Consider the following about your setup:
1316

1417
* Connection to Loki (as defined in the `FlowCollector` CR `spec.loki` parameter)
1518
* Connection to Kafka (as defined in the `FlowCollector` CR `spec.kafka` parameter)
@@ -33,9 +36,9 @@ metadata:
3336
spec:
3437
namespace: netobserv
3538
networkPolicy:
36-
enable: true <1>
39+
enable: true <1>
3740
additionalNamespaces: ["openshift-console", "openshift-monitoring"] <2>
3841
# ...
3942
----
40-
<1> By default, the `enable` value is `false`.
43+
<1> By default, the `enable` value is `true`.
4144
<2> Default values are `["openshift-console", "openshift-monitoring"]`.

observability/network_observability/network-observability-network-policy.adoc

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,12 +7,10 @@ include::_attributes/common-attributes.adoc[]
77

88
toc::[]
99

10-
As a user with the `admin` role, you can create a network policy for the `netobserv` namespace to secure inbound access to the Network Observability Operator.
10+
As a user with the `admin` role, you can create a network policy for the `netobserv` namespace to secure inbound and outbound access to the Network Observability Operator.
1111

1212
include::modules/network-observability-deploy-network-policy.adoc[leveloffset=+1]
1313

14-
include::modules/network-observability-create-network-policy.adoc[leveloffset=+1]
15-
1614
[role="_additional-resources"]
1715
.Additional resources
1816
* xref:../../networking/network_security/network_policy/creating-network-policy.adoc#nw-networkpolicy-object_creating-network-policy[Creating a network policy using the CLI]

0 commit comments

Comments
 (0)