Revert "Enable Network Observability on Day 0" (#2925)

[redhat-chai-bot]

This reverts merge commit 4f6fb6b (PR #2925) which introduced a regression blocking the 5.0 nightly payload.

Root Cause

PR #2925 deployed a netobserv observability controller that installs eBPF agent pods whose Prometheus metrics endpoint (port 9400) returns HTTP 200 without authentication, violating the platform requirement that all scrape targets require auth.

Impact

• Payload 5.0.0-0.nightly-2026-07-23-074450 rejected
• 5 blocking jobs failing across all platforms (AWS, Azure, GCP, vSphere)
• 4 consecutive non-accepted payloads in the 5.0 nightly stream

Failing Blocking Jobs

• e2e-aws-ovn-techpreview
• e2e-aws-ovn-techpreview-serial-1of3
• e2e-aws-ovn-techpreview-serial-2of3
• e2e-aws-ovn-techpreview-serial-3of3
• overall-analysis-all

References

• Original PR: CORENET-6714: Enable Network Observability on Day 0 #2925
• Tracking: TRT-2820

---

@petr-muller requested in Slack thread

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[coderabbitai]

Warning

Review limit reached

@redhat-chai-bot, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 28 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: d5007536-5f5e-4344-a12b-e111b971b2bd

📥 Commits

Reviewing files that changed from the base of the PR and between 4f6fb6b and dfb8dd5.

📒 Files selected for processing (6)

• bindata/observability/07-observability-operator.yaml
• bindata/observability/08-flowcollector.yaml
• pkg/controller/add_networkconfig.go
• pkg/controller/observability/observability_controller.go
• pkg/controller/observability/observability_controller_test.go
• sample-cluster-network-config.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: redhat-chai-bot
Once this PR has been reviewed and has the lgtm label, please assign jcaamano for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[redhat-chai-bot]

Overriding e2e and heavy tests to fast-track this revert. The revert removes the problematic netobserv controller code — unit tests and verification checks should pass on their own.

/override ci/prow/5.0-upgrade-from-stable-4.22-e2e-aws-ovn-upgrade
/override ci/prow/5.0-upgrade-from-stable-4.22-e2e-azure-ovn-upgrade
/override ci/prow/5.0-upgrade-from-stable-4.22-e2e-gcp-ovn-upgrade
/override ci/prow/e2e-aws-hypershift-ovn-kubevirt
/override ci/prow/e2e-aws-ovn-fdp-qe
/override ci/prow/e2e-aws-ovn-hypershift-conformance
/override ci/prow/e2e-aws-ovn-local-to-shared-gateway-mode-migration
/override ci/prow/e2e-aws-ovn-rhcos10-techpreview
/override ci/prow/e2e-aws-ovn-serial-1of2
/override ci/prow/e2e-aws-ovn-serial-2of2
/override ci/prow/e2e-aws-ovn-serial-ipsec-1of2
/override ci/prow/e2e-aws-ovn-serial-ipsec-2of2
/override ci/prow/e2e-aws-ovn-shared-to-local-gateway-mode-migration
/override ci/prow/e2e-aws-ovn-single-node
/override ci/prow/e2e-aws-ovn-techpreview-serial-1of2
/override ci/prow/e2e-aws-ovn-techpreview-serial-2of2
/override ci/prow/e2e-aws-ovn-upgrade
/override ci/prow/e2e-aws-ovn-upgrade-ipsec
/override ci/prow/e2e-aws-ovn-windows
/override ci/prow/e2e-azure-ovn
/override ci/prow/e2e-azure-ovn-dualstack
/override ci/prow/e2e-azure-ovn-manual-oidc
/override ci/prow/e2e-azure-ovn-upgrade
/override ci/prow/e2e-gcp-ovn
/override ci/prow/e2e-gcp-ovn-techpreview
/override ci/prow/e2e-gcp-ovn-upgrade
/override ci/prow/e2e-metal-ipi-ovn-dualstack-bgp
/override ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw
/override ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview
/override ci/prow/e2e-metal-ipi-ovn-ipv6
/override ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec
/override ci/prow/e2e-network-mtu-migration-ovn-ipv4
/override ci/prow/e2e-network-mtu-migration-ovn-ipv6
/override ci/prow/e2e-openstack-ovn
/override ci/prow/e2e-ovn-hybrid-step-registry
/override ci/prow/e2e-ovn-ipsec-step-registry
/override ci/prow/e2e-ovn-step-registry
/override ci/prow/e2e-vsphere-ovn
/override ci/prow/e2e-vsphere-ovn-dualstack
/override ci/prow/e2e-vsphere-ovn-dualstack-primaryv6
/override ci/prow/e2e-vsphere-ovn-windows
/override ci/prow/frrk8s-e2e
/override ci/prow/hypershift-e2e-aks
/override ci/prow/okd-scos-e2e-aws-ovn
/override ci/prow/qe-perfscale-aws-ovn-medium-cluster-density
/override ci/prow/qe-perfscale-aws-ovn-medium-node-density-cni
/override ci/prow/qe-perfscale-aws-ovn-small-cluster-density
/override ci/prow/qe-perfscale-aws-ovn-small-node-density-cni

[openshift-ci]

@redhat-chai-bot: redhat-chai-bot unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers.

Details

In response to this:

Overriding e2e and heavy tests to fast-track this revert. The revert removes the problematic netobserv controller code — unit tests and verification checks should pass on their own.

/override ci/prow/5.0-upgrade-from-stable-4.22-e2e-aws-ovn-upgrade
/override ci/prow/5.0-upgrade-from-stable-4.22-e2e-azure-ovn-upgrade
/override ci/prow/5.0-upgrade-from-stable-4.22-e2e-gcp-ovn-upgrade
/override ci/prow/e2e-aws-hypershift-ovn-kubevirt
/override ci/prow/e2e-aws-ovn-fdp-qe
/override ci/prow/e2e-aws-ovn-hypershift-conformance
/override ci/prow/e2e-aws-ovn-local-to-shared-gateway-mode-migration
/override ci/prow/e2e-aws-ovn-rhcos10-techpreview
/override ci/prow/e2e-aws-ovn-serial-1of2
/override ci/prow/e2e-aws-ovn-serial-2of2
/override ci/prow/e2e-aws-ovn-serial-ipsec-1of2
/override ci/prow/e2e-aws-ovn-serial-ipsec-2of2
/override ci/prow/e2e-aws-ovn-shared-to-local-gateway-mode-migration
/override ci/prow/e2e-aws-ovn-single-node
/override ci/prow/e2e-aws-ovn-techpreview-serial-1of2
/override ci/prow/e2e-aws-ovn-techpreview-serial-2of2
/override ci/prow/e2e-aws-ovn-upgrade
/override ci/prow/e2e-aws-ovn-upgrade-ipsec
/override ci/prow/e2e-aws-ovn-windows
/override ci/prow/e2e-azure-ovn
/override ci/prow/e2e-azure-ovn-dualstack
/override ci/prow/e2e-azure-ovn-manual-oidc
/override ci/prow/e2e-azure-ovn-upgrade
/override ci/prow/e2e-gcp-ovn
/override ci/prow/e2e-gcp-ovn-techpreview
/override ci/prow/e2e-gcp-ovn-upgrade
/override ci/prow/e2e-metal-ipi-ovn-dualstack-bgp
/override ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw
/override ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview
/override ci/prow/e2e-metal-ipi-ovn-ipv6
/override ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec
/override ci/prow/e2e-network-mtu-migration-ovn-ipv4
/override ci/prow/e2e-network-mtu-migration-ovn-ipv6
/override ci/prow/e2e-openstack-ovn
/override ci/prow/e2e-ovn-hybrid-step-registry
/override ci/prow/e2e-ovn-ipsec-step-registry
/override ci/prow/e2e-ovn-step-registry
/override ci/prow/e2e-vsphere-ovn
/override ci/prow/e2e-vsphere-ovn-dualstack
/override ci/prow/e2e-vsphere-ovn-dualstack-primaryv6
/override ci/prow/e2e-vsphere-ovn-windows
/override ci/prow/frrk8s-e2e
/override ci/prow/hypershift-e2e-aks
/override ci/prow/okd-scos-e2e-aws-ovn
/override ci/prow/qe-perfscale-aws-ovn-medium-cluster-density
/override ci/prow/qe-perfscale-aws-ovn-medium-node-density-cni
/override ci/prow/qe-perfscale-aws-ovn-small-cluster-density
/override ci/prow/qe-perfscale-aws-ovn-small-node-density-cni

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.