Skip to content

[cherry-pick: release-v0.81.x] revert(operator): remove NetworkPolicy from operator bundle manifests - #3877

Merged
tekton-robot merged 1 commit into
release-v0.81.xfrom
cherry-pick-3873-to-release-v0.81.x
Aug 7, 2026
Merged

[cherry-pick: release-v0.81.x] revert(operator): remove NetworkPolicy from operator bundle manifests#3877
tekton-robot merged 1 commit into
release-v0.81.xfrom
cherry-pick-3873-to-release-v0.81.x

Conversation

@tekton-robot

Copy link
Copy Markdown
Contributor

This is a cherry-pick of #3873


Changes

Removes the static NetworkPolicy manifests added to the operator bundle by #3714:

  • config/kubernetes/base/networkpolicy.yaml (deleted)
  • config/openshift/base/networkpolicy.yaml (deleted)
  • config/kubernetes/base/kustomization.yaml (entry removed)
  • config/openshift/base/kustomization.yaml (entry removed)
  • docs/NetworkPolicy.md (operator namespace section removed)

Why

OLM v1 does not support NetworkPolicy resources in operator bundles. Shipping these as static manifests alongside the operator Deployment/RBAC causes install failures on OLM v1 clusters.

The reconciler-managed NetworkPolicies for operand namespaces (proxy-webhook, pipeline core, triggers, chains, PAC, pruner, results, multicluster, etc.) are not affected — those are applied by the operator's own reconcilers and are unrelated to the bundle manifests.

Related

Partial revert of #3714 (static-manifest portion only).

Made with Cursor

OLM v1 does not support NetworkPolicy resources in operator bundles.
Remove config/kubernetes/base/networkpolicy.yaml and
config/openshift/base/networkpolicy.yaml (and their kustomization
entries) added by #3714. The reconciler-managed NetworkPolicies for
operand namespaces (proxy-webhook, pipeline, triggers, chains, etc.)
are unaffected.

Reverts the static-manifest portion of #3714.

Signed-off-by: Jawed khelil <jkhelil@redhat.com>
Assisted-by: Claude Sonnet 4.6 (via Cursor)
Co-authored-by: Cursor <cursoragent@cursor.com>
@tekton-robot tekton-robot added the do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. label Aug 7, 2026
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Aug 7, 2026
@pratap0007

Copy link
Copy Markdown
Contributor

/approve

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 7, 2026
@jkhelil

jkhelil commented Aug 7, 2026

Copy link
Copy Markdown
Member

/release-note-none

@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Aug 7, 2026
@pratap0007

Copy link
Copy Markdown
Contributor

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 7, 2026
@jkhelil

jkhelil commented Aug 7, 2026

Copy link
Copy Markdown
Member

/approve

@tekton-robot

Copy link
Copy Markdown
Contributor Author

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jkhelil, pratap0007

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@tekton-robot
tekton-robot merged commit 7665e0b into release-v0.81.x Aug 7, 2026
13 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. 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.

3 participants