OSDOCS-17361 [NETOBSERV] Refactor release notes 1.9.1

[gwynnemonahan]

OSDOCS-17361 [NETOBSERV] Refactor release notes 1.9.1

Version(s):
4.12, 4.14+

Rel notes refactor gets cherry-picked back to 4.12, 4.14, and 4.15

Issue:
https://issues.redhat.com/browse/OSDOCS-17361

Link to docs preview:

• 1.9.1 advisory: https://102709--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/release_notes_archive/network-observability-operator-release-notes-archive.html#network-observability-operator-release-notes-1-9-1_network-observability-operator-archived-release-notes
• 1.9.1 fixed issues: https://102709--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/release_notes_archive/network-observability-operator-release-notes-archive.html#network-observability-operator-release-notes-1-9-1-fixed-issues_network-observability-operator-archived-release-notes

QE review:
QE is not required for this PR. This PR modularizes Network Observability Operator release notes for 1.9.1 only. There are no content changes.

Additional information:

• The Network Observability Operator release notes are being modularized through a series of PRs. This means that things will get cleaned up and consolidated along the way.
• Some of these PRs may contain updates to previously merged content for the purpose of consistency.
• The network-observability-release-notes.adoc file will dwindle with each PR while the network-observability-operator-release-notes-archive.adoc file will grow.
  In as many cases as possible, such as:
  [id="network-observability-channel-removal-1.4_{context}"]
  == Channel removal
  existing ID in network-observability-release-notes.adoc has been used in the new module.
• Since not all content applies to every OCP branch, it is possible there will be cherry-pick failures. This will likely apply to release notes since it has been 1 assembly file and not all content is applicable to all OCP branches.
• I will manually verify content on each breach, and create manual cherry-picks accordingly.

---

• OSDOCS-15830 [NETOBSERV] Refactor release notes 1.9.0 #102641 must be merged first. Then rebase to capture 1.9.0 .
  • Rebased 11/19/2025 AM. Captured 1.9.0 from OSDOCS-15830 [NETOBSERV] Refactor release notes 1.9.0 #102641 .

---

• By this PR:
  • Rel notes for 1.1.0-1.6.2 including all z-streams, have been modularized.
    • 52 new modules have been created for 1.1.0-1.9.0 including all z-streams.
    • 2 new modules are added with this PR
  • Rel notes for 1.8.0, 1.8.1, 1.9.0,and 1.9.1 remain.
  • Rel notes for 1.9.2, 1.9.3, and 1.10.0 were modularized from the start as they were released when the new format was announced.
  • 1.9.2 and 1.9.3 are already in release_notes_archive
  • 1.10.0 can be moved to release_notes until 1.10.1
  • 1.10.1 modules will replace 1.10.0 modules in release_notes
  • 1.10.0 modules will be moved to release_notes_archive
  • Update stub to point to release_notes

[ocpdocs-previewbot]

🤖 Wed Nov 19 13:58:07 - Prow CI generated the docs preview:

https://102709--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/release_notes_archive/network-observability-operator-release-notes-archive.html

[gwynnemonahan]

Rebased 11/19/2025 AM. Captured 1.9.0 from #102641 .

[openshift-ci]

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

[gwynnemonahan]

/label merge-review-needed

[skopacz1]

LGTM

[skopacz1]

/cherrypick enterprise-4.12

[skopacz1]

/cherrypick enterprise-4.14

[skopacz1]

/cherrypick enterprise-4.15
/cherrypick enterprise-4.16
/cherrypick enterprise-4.17
/cherrypick enterprise-4.18
/cherrypick enterprise-4.19
/cherrypick enterprise-4.20
/cherrypick enterprise-4.21

[openshift-cherrypick-robot]

@skopacz1: new pull request created: #102841

Details

In response to this:

/cherrypick enterprise-4.12

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.

[openshift-cherrypick-robot]

@skopacz1: new pull request created: #102842

Details

In response to this:

/cherrypick enterprise-4.14

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.

[openshift-cherrypick-robot]

@skopacz1: new pull request created: #102843

Details

In response to this:

/cherrypick enterprise-4.15
/cherrypick enterprise-4.16
/cherrypick enterprise-4.17
/cherrypick enterprise-4.18
/cherrypick enterprise-4.19
/cherrypick enterprise-4.20
/cherrypick enterprise-4.21

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.

[openshift-cherrypick-robot]

@skopacz1: new pull request created: #102845

Details

In response to this:

/cherrypick enterprise-4.15
/cherrypick enterprise-4.16
/cherrypick enterprise-4.17
/cherrypick enterprise-4.18
/cherrypick enterprise-4.19
/cherrypick enterprise-4.20
/cherrypick enterprise-4.21

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.

[openshift-cherrypick-robot]

@skopacz1: new pull request created: #102846

Details

In response to this:

/cherrypick enterprise-4.15
/cherrypick enterprise-4.16
/cherrypick enterprise-4.17
/cherrypick enterprise-4.18
/cherrypick enterprise-4.19
/cherrypick enterprise-4.20
/cherrypick enterprise-4.21

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.

[openshift-cherrypick-robot]

@skopacz1: new pull request created: #102847

Details

In response to this:

/cherrypick enterprise-4.15
/cherrypick enterprise-4.16
/cherrypick enterprise-4.17
/cherrypick enterprise-4.18
/cherrypick enterprise-4.19
/cherrypick enterprise-4.20
/cherrypick enterprise-4.21

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.

[openshift-cherrypick-robot]

@skopacz1: new pull request created: #102848

Details

In response to this:

/cherrypick enterprise-4.15
/cherrypick enterprise-4.16
/cherrypick enterprise-4.17
/cherrypick enterprise-4.18
/cherrypick enterprise-4.19
/cherrypick enterprise-4.20
/cherrypick enterprise-4.21

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.

[openshift-cherrypick-robot]

@skopacz1: new pull request created: #102849

Details

In response to this:

/cherrypick enterprise-4.15
/cherrypick enterprise-4.16
/cherrypick enterprise-4.17
/cherrypick enterprise-4.18
/cherrypick enterprise-4.19
/cherrypick enterprise-4.20
/cherrypick enterprise-4.21

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.

[openshift-cherrypick-robot]

@skopacz1: new pull request created: #102850

Details

In response to this:

/cherrypick enterprise-4.15
/cherrypick enterprise-4.16
/cherrypick enterprise-4.17
/cherrypick enterprise-4.18
/cherrypick enterprise-4.19
/cherrypick enterprise-4.20
/cherrypick enterprise-4.21

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.