Skip to content

OSDOCS-19153 [NETOBSERV] 1.12 Technology Preview Network Observability Operator Day 0 - #111382

Open
gwynnemonahan wants to merge 1 commit into
openshift:mainfrom
gwynnemonahan:OSDOCS-19153
Open

OSDOCS-19153 [NETOBSERV] 1.12 Technology Preview Network Observability Operator Day 0#111382
gwynnemonahan wants to merge 1 commit into
openshift:mainfrom
gwynnemonahan:OSDOCS-19153

Conversation

@gwynnemonahan

@gwynnemonahan gwynnemonahan commented May 7, 2026

Copy link
Copy Markdown
Contributor

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.
  • Uncomment Technology Preview section in 1.12 rel notes
  • 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 updates

Version(s):
4.22+

Issue:
https://redhat.atlassian.net/browse/OSDOCS-19153

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

  • Check with Gwynne before merging.
  • 05/07/2026: Initial PR created to work through information architecture between Networking and Observiability > Network Observability

@openshift-ci openshift-ci Bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label May 7, 2026
@ocpdocs-previewbot

ocpdocs-previewbot commented May 7, 2026

Copy link
Copy Markdown

🤖 Tue Aug 18 15:57:47 - Prow CI generated the docs preview:
https://111382--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt

Comment thread modules/network-observability-day-0-getting-started.adoc Outdated
@openshift-ci openshift-ci Bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels May 11, 2026
Comment thread modules/network-observability-enabling-feature-gate-existing-cluster.adoc Outdated
Comment thread modules/network-observability-enabling-feature-gate.adoc Outdated
Comment thread modules/nw-operator-cr.adoc Outdated
Comment thread modules/network-observability-day-0-do-not-install.adoc Outdated
Comment thread modules/network-observability-day-0-getting-started.adoc Outdated
Comment thread modules/network-observability-day-0-getting-started.adoc Outdated
Comment thread modules/network-observability-day-0-install-and-enable.adoc Outdated
Comment thread modules/network-observability-day-0-install-and-enable.adoc Outdated
Comment thread modules/network-observability-enabling.adoc Outdated
Comment thread modules/network-observability-enabling.adoc Outdated
Comment thread modules/network-observability-day-0-architecture.adoc Outdated
Comment thread modules/network-observability-day-0-getting-started.adoc Outdated
@gwynnemonahan

Copy link
Copy Markdown
Contributor Author

Rebased 05/26/2026 PM.

@gwynnemonahan
gwynnemonahan force-pushed the OSDOCS-19153 branch 2 times, most recently from 6e900dc to ff59d9b Compare May 29, 2026 17:47
@gwynnemonahan

Copy link
Copy Markdown
Contributor Author

Rebased 05/29/2026 to capture stub page from #111600

@gwynnemonahan

Copy link
Copy Markdown
Contributor Author

Rebased 06/09/2026 to capture no-1.12 integration branch merge.

@gwynnemonahan gwynnemonahan added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 11, 2026
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 12, 2026
@gwynnemonahan

Copy link
Copy Markdown
Contributor Author

Rebased 06/12/2026 PM.

@gwynnemonahan gwynnemonahan added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 12, 2026
@gwynnemonahan

Copy link
Copy Markdown
Contributor Author

Rebased 06/22/2026 AM.

@gwynnemonahan

gwynnemonahan commented Jun 30, 2026

Copy link
Copy Markdown
Contributor Author

Rebased 06/30/2026 AM.

@gwynnemonahan

Copy link
Copy Markdown
Contributor Author

07/07/2026: Rebased PM.


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.

Network observability helps you:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"helps you" is anthrophomorpism. Maybe:

You can use Network observability to complete the following tasks:

Comment thread modules/network-observability-automatic-installation-overview.adoc
[id="prerequisites-for-network-observability-automatic-installation_{context}"]
== Prerequisites for automatic network observability installation (Technology Preview)

Network Observability automatic installation is a Technology Preview feature that requires the `NetworkObservabilityInstall` feature gate. To use this feature during cluster installation, you must:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Network Observability automatic installation is a Technology Preview feature that requires the `NetworkObservabilityInstall` feature gate. To use this feature during cluster installation, you must:
Network Observability automatic installation is a Technology Preview feature that requires the `NetworkObservabilityInstall` feature gate. To use this feature during cluster installation, you must complete the following tasks:

Comment thread modules/network-observability-automatic-installation-overview.adoc
[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), then sets the `NetworkObservabilityDeployed` condition in the Network CR status.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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), then sets the `NetworkObservabilityDeployed` condition in the Network CR status.
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.

Better align with IBM SG around use of "then".


After cluster creation, the CNO sets the `NetworkObservabilityDeployed` condition when the Operator deploys successfully.

If you omit `installationPolicy`, which then installs Network Observability Operator, the CNO will not reinstall the operator if you remove it later.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you omit `installationPolicy`, which then installs Network Observability Operator, the CNO will not reinstall the operator if you remove it later.
If you omit `installationPolicy`, which then installs Network Observability Operator, the CNO will not reinstall the Operator if you remove it later.

Check for any other instances that need changing.


[IMPORTANT]
====
This Technology Preview feature is intended for testing and development environments with {product-title} 4.22. The feature gate requirement is temporary until this feature reaches General Availability (GA).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This TP note does not exactly follow the typical template.

.Prerequisites

* You have access to the cluster as a user with the `cluster-admin` role.
* The OpenShift CLI (`oc`) is installed.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* The OpenShift CLI (`oc`) is installed.
* The {oc-first} is installed.


:_mod-docs-content-type: CONCEPT
[id="network-observability-automatic-installation-overview_{context}"]
= Understand automatic network observability installation

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe the following noun phrase might work better for the concept module:

Automatic network observability installation

@gwynnemonahan

Copy link
Copy Markdown
Contributor Author

Rebased 07/20/2026 AM.

@gwynnemonahan

Copy link
Copy Markdown
Contributor Author

Rebased 07/28/2026 PM.

@gwynnemonahan

Copy link
Copy Markdown
Contributor Author

Rebased 08/05/2026 PM.

@gwynnemonahan

Copy link
Copy Markdown
Contributor Author

Rebased 08/12/2026 PM.

@gwynnemonahan

Copy link
Copy Markdown
Contributor Author

/retest

@gwynnemonahan

Copy link
Copy Markdown
Contributor Author

Rebased 08/18/2026 AM.

@openshift-ci

openshift-ci Bot commented Aug 18, 2026

Copy link
Copy Markdown

@gwynnemonahan: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.22 branch/enterprise-5.0 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants