Skip to content

Add NetworkPolicy RBAC permission#76

Draft
mpryc wants to merge 1 commit into
medik8s:mainfrom
mpryc:add-networkpolicy-rbac
Draft

Add NetworkPolicy RBAC permission#76
mpryc wants to merge 1 commit into
medik8s:mainfrom
mpryc:add-networkpolicy-rbac

Conversation

@mpryc

@mpryc mpryc commented Jul 22, 2026

Copy link
Copy Markdown

Summary

Add networking.k8s.io/networkpolicies RBAC (create, delete, update) to allow managing NetworkPolicies for operand workloads.

Changes

  • Add kubebuilder RBAC marker to controller
  • Regenerate config/rbac/role.yaml
  • Regenerate bundle CSV

Test plan

  • make manifests — RBAC generated correctly
  • make bundle-reset — bundle validates successfully

🤖 Generated with Claude Code

Add networking.k8s.io/networkpolicies RBAC (create, delete, update)
to allow managing NetworkPolicies for operand workloads.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Michal Pryc <mpryc@redhat.com>
@openshift-ci

openshift-ci Bot commented Jul 22, 2026

Copy link
Copy Markdown

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@mpryc, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 618b5c44-17cf-481a-a062-0bc34098cfdc

📥 Commits

Reviewing files that changed from the base of the PR and between 0b200c5 and 267695f.

📒 Files selected for processing (3)
  • bundle/manifests/storage-based-remediation.clusterserviceversion.yaml
  • config/rbac/role.yaml
  • internal/controller/storagebasedremediationconfig_controller.go
✨ 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

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

@openshift-ci

openshift-ci Bot commented Jul 22, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mpryc

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

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant