OCPBUGS-62517: Add PodDisruptionBudget permissions to cluster-olm-operator

[jianzhangbjz]

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)

[openshift-ci-robot]

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

Details

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]

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

@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

[jianzhangbjz]

Test passed. https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-cluster-olm-operator-152-openshift-operator-framework-operator-controller-568-ci-4.21-e2e-azure-ovn-upgrade/1994322786000048128
/verified by @jianzhangbjz

[openshift-ci-robot]

@jianzhangbjz: This PR has been marked as verified by @jianzhangbjz.

Details

In response to this:

Test passed. https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-cluster-olm-operator-152-openshift-operator-framework-operator-controller-568-ci-4.21-e2e-azure-ovn-upgrade/1994322786000048128
/verified by @jianzhangbjz

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.

[jianzhangbjz]

/retest-required

[openshift-ci]

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

[dtfranz]

/lgtm

[jianzhangbjz]

/approve

[perdasilva]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jianzhangbjz, perdasilva

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:

• OWNERS [perdasilva]

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

[openshift-ci-robot]

@jianzhangbjz: Jira Issue OCPBUGS-62517: Some pull requests linked via external trackers have merged:

• operator-framework/operator-controller#2263
• openshift/operator-framework-operator-controller#519
• operator-framework/operator-controller#2362

The following pull request, linked via external tracker, has not merged:

• openshift/operator-framework-operator-controller#568 is closed

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-62517 has not been moved to the MODIFIED state.

This PR is marked as verified. If the remaining PRs listed above are marked as verified before merging, the issue will automatically be moved to VERIFIED after all of the changes from the PRs are available in an accepted nightly payload.

Details

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.