此内容没有您所选择的语言版本。
Chapter 7. Network Policy
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.
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.
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.
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:
-
Connection to Loki (as defined in the
FlowCollectorCRspec.lokiparameter) -
Connection to Kafka (as defined in the
FlowCollectorCRspec.kafkaparameter) -
Connection to any exporter (as defined in FlowCollector CR
spec.exportersparameter) -
If you are using Loki and including it in the policy target, connection to an external object storage (as defined in your
LokiStackrelated secret)
Procedure
-
In the web console, go to Operators
Installed Operators page. - Under the Provided APIs heading for Network Observability, select Flow Collector.
- Select cluster then select the YAML tab.
Configure the
FlowCollectorCR. A sample configuration is as follows:Example
FlowCollectorCR for network policyCopy to Clipboard Copied! Toggle word wrap Toggle overflow