OSDOCS-19153 [NETOBSERV] 1.12 Technology Preview Network Observability Operator Day 0 - #111382
OSDOCS-19153 [NETOBSERV] 1.12 Technology Preview Network Observability Operator Day 0#111382gwynnemonahan wants to merge 5 commits into
Conversation
openshift-ci
Bot
added
the
size/L
|
🤖 Thu Sep 10 16:39:29 - Prow CI generated the docs preview: |
4f1dd2f to
706870b
Compare
openshift-ci
Bot
added
size/XL
d64d0a4 to
fe8e28e
Compare
f5a6b2d to
98b11a9
Compare
|
Rebased 05/26/2026 PM. |
6e900dc to
ff59d9b
Compare
|
Rebased 05/29/2026 to capture stub page from #111600 |
d6ee8bc to
74267e8
Compare
|
Rebased 07/20/2026 AM. |
74267e8 to
3ebde6e
Compare
|
Rebased 07/28/2026 PM. |
3ebde6e to
61c5d50
Compare
|
Rebased 08/05/2026 PM. |
61c5d50 to
60cde15
Compare
|
Rebased 08/12/2026 PM. |
|
/retest |
60cde15 to
80bef5e
Compare
|
Rebased 08/18/2026 AM. |
80bef5e to
96b2430
Compare
|
Rebased 09/03/2026 AM. |
openshift-ci
Bot
removed
the
do-not-merge/work-in-progress
755f6a1 to
ffd6e67
Compare
|
Rebase 09/03/2026 PM. |
ffd6e67 to
3cbf002
Compare
|
Rebased 09/10/2026 AM. |
openshift-ci
Bot
added
size/XL
|
@gwynnemonahan: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
| installationPolicy: | ||
| |Controls whether the Network Observability Operator is automatically installed during cluster creation. This field is available only when the `NetworkObservabilityInstall` feature gate is enabled. | ||
|
|
||
| When set to `InstallAndEnable`, the Cluster Network Operator installs the Network Observability Operator and creates a default FlowCollector during cluster creation. The CNO monitors the installation and reinstalls the operator if it is removed. |
There was a problem hiding this comment.
If you set to InstallAndEnable, it will also install on SNO clusters. That's the difference between explicitly setting this value and omitting the value.
It also does not reinstall. (Note: This was a more recent change.)
|
|
||
| You can use Network observability to complete the following tasks: | ||
|
|
||
| * Monitor network traffic flows between pods, services, and external endpoints. |
There was a problem hiding this comment.
If you are referring to general Network Observability, then this is okay. This feature configures Network Observability with no Loki so there are no flows. Maybe just remove the word "flow"?
|
|
||
| The following cluster types do not enable network observability by default: | ||
|
|
||
| * {sno-caps} clusters, due to resource constraints. |
There was a problem hiding this comment.
It will enable NetworkObservability if the installation policy is set to "InstallAndEnable".
| The following cluster types do not enable network observability by default: | ||
|
|
||
| * {sno-caps} clusters, due to resource constraints. | ||
| * Clusters where you disabled network observability in the installation configuration. |
There was a problem hiding this comment.
To be explicit, this occurs when the installation policy is set to "NoAction".
| Network topology visualization:: Explore visual representations of network traffic flows between namespaces, workloads, and nodes. | ||
|
|
||
| Metrics and dashboards:: Access Prometheus metrics and Grafana dashboards that track network performance indicators including throughput, packet drops, and connection counts. | ||
|
|
There was a problem hiding this comment.
This might be the right place to say if you want flows and features that require flows, you need to configure a LokiStack.
| The automatic network observability installation occurs during cluster creation and upgrade. The Cluster Network Operator (CNO) installs the Network Observability Operator and creates a default `FlowCollector` custom resource (CR), and then sets the `NetworkObservabilityDeployed` condition in the Network CR status. | ||
|
|
||
| After successful deployment with the default policy, the CNO does not monitor or manage the Network Observability Operator. If you delete the Network Observability Operator or the `FlowCollector` resource, they are not automatically reinstalled. | ||
|
|
There was a problem hiding this comment.
You could put an asterisk here and then let the user know there is a way to effectively "reset it back to the factory default" behavior. To do this, enter oc edit network.operator cluster --subresource=status and remove the status entry associated with 'type: NetworkObservabilityDeployed'. Now it looks like a brand new cluster.
|
|
||
| After successful deployment with the default policy, the CNO does not monitor or manage the Network Observability Operator. If you delete the Network Observability Operator or the `FlowCollector` resource, they are not automatically reinstalled. | ||
|
|
||
| If you set `installationPolicy` to `InstallAndEnable` in your `install-config.yaml` file, the CNO continues to monitor the installation and reinstalls the Network Observability Operator if you remove it. The CNO does not manage the `FlowCollector` resource because it is managed by the Network Observability Operator. |
There was a problem hiding this comment.
It doesn't reinstall anymore. The previous statement "If you delete the Network Observability Operator or the FlowCollector resource, they are not automatically reinstalled." is the correct one.
| For production deployments, Red Hat recommends using the standard `postinstallation` method to install the Network Observability Operator. | ||
| ==== | ||
|
|
||
| On {product-title} 4.22 clusters with the `NetworkObservabilityInstall` feature gate enabled, the Network Observability Operator and its dependencies are automatically installed and configured during cluster creation. This provides immediate access to network traffic monitoring capabilities through the {product-title} web console. |
| * *Agent type*: eBPF with DNS tracking enabled | ||
| * *Sampling rate*: 400 (collects 1 in every 400 flows) | ||
| * *Deployment model*: Service | ||
| * *Loki storage*: Disabled (flows are not persisted) |
| [id="deployment-lifecycle_{context}"] | ||
| == Deployment lifecycle | ||
|
|
||
| The automatic network observability installation occurs during cluster creation and upgrade. The Cluster Network Operator (CNO) installs the Network Observability Operator and creates a default `FlowCollector` custom resource (CR), and then sets the `NetworkObservabilityDeployed` condition in the Network CR status. |
There was a problem hiding this comment.
It only occurs in OCP 5+ when the cluster is created or in OCP 4.22 upgrade to 5.0. To be clear, it doesn't occur on every upgrade.
8 participants
OSDOCS-19153 [NETOBSERV] 1.12 Technology Preview Network Observability Operator Day 0
NOTES
Do not merge until CORENET-6714: Enable Network Observability on Day 0 cluster-network-operator#2925 has been merged.This is a work-in-progress as the information architecture continues to be worked out.Use of "Network Observability Operator Day 0" is a placeholder.Headers/titles are likely to change prior to formal reviews.Cluster Network Operator CR updatesVersion(s):
5.0+
Issue:
https://redhat.atlassian.net/browse/OSDOCS-19153
Link to docs preview:
NETWORKING
NETWORK OBSERVABILITY OPERATOR
QE review:
Additional information:
05/07/2026: Initial PR created to work through information architecture between Networking and Observiability > Network Observability