Skip to content

Update Docs #2187

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
luisjira merged 1 commit into from
Nov 26, 2025
Merged

Update Docs #2187

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions docs/flowcollector-flows-netobserv-io-v1beta2.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ Type::
| `string`
| `deploymentModel` defines the desired type of deployment for flow processing. Possible values are: +

- `Direct` (default) to make the flow processor listen directly from the agents. +
- `Direct` (default) to make the flow processor listen directly from the agents. Only recommended on small clusters, below 15 nodes. +

- `Kafka` to make flows sent to a Kafka pipeline before consumption by the processor. +

Expand Down Expand Up @@ -2672,9 +2672,10 @@ configuration, you can disable it and install your own instead.

| `enable`
| `boolean`
| Set `enable` to `true` to deploy network policies on the namespaces used by Network Observability (main and privileged). It is disabled by default.
These network policies better isolate the Network Observability components to prevent undesired connections to them.
This option is enabled by default, disable it to manually manage network policies
| Deploys network policies on the namespaces used by Network Observability (main and privileged).
These network policies better isolate the Network Observability components to prevent undesired connections from and to them.
This option is enabled by default when using with OVNKubernetes, and disabled otherwise (it has not been tested with other CNIs).
When disabled, you can manually create the network policies for the Network Observability components.

|===
== .spec.processor
Expand Down