Skip to content

Conversation

@jianzhangbjz
Copy link
Member

The cluster-olm-operator needs permissions to manage PodDisruptionBudgets as they are now part of the static operand assets for catalogd and operator-controller to ensure high availability during upgrades.

This change adds the necessary RBAC permissions for the policy API group to create, update, patch, get, list, watch, and delete poddisruptionbudgets.

Fixes: openshift/operator-framework-operator-controller#568 (comment)

The cluster-olm-operator needs permissions to manage PodDisruptionBudgets
as they are now part of the static operand assets for catalogd and
operator-controller to ensure high availability during upgrades.

This change adds the necessary RBAC permissions for the policy API group
to create, update, patch, get, list, watch, and delete poddisruptionbudgets.

Fixes: openshift/operator-framework-operator-controller#568
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Nov 28, 2025
@openshift-ci-robot
Copy link

@jianzhangbjz: This pull request references Jira Issue OCPBUGS-62517, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

The cluster-olm-operator needs permissions to manage PodDisruptionBudgets as they are now part of the static operand assets for catalogd and operator-controller to ensure high availability during upgrades.

This change adds the necessary RBAC permissions for the policy API group to create, update, patch, get, list, watch, and delete poddisruptionbudgets.

Fixes: openshift/operator-framework-operator-controller#568 (comment)

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from anik120 and oceanc80 November 28, 2025 08:26
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 28, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 28, 2025

@jianzhangbjz: This PR was included in a payload test run from openshift/operator-framework-operator-controller#568
trigger 0 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 28, 2025

@jianzhangbjz: This PR was included in a payload test run from openshift/operator-framework-operator-controller#568
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.21-e2e-azure-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/5ff73e90-cc34-11f0-96e3-b060b7dc0c8c-0

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

Labels

jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants