Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(operator): Fix RBAC permission for poddisruptionbudgets #15107

Merged
merged 1 commit into from
Nov 27, 2024

Conversation

xperimental
Copy link
Collaborator

What this PR does / why we need it:

This PR fixes an RBAC issue accidentally introduced by #14817. The current permission references policy/v1 as an API group which is not valid (groups do not contain a version).

The current state causes the operator to stop working once it tries to interact with PodDisruptionBudget resources, because it can not recover from the error returned by the API.

Which issue(s) this PR fixes:

Special notes for your reviewer:

Checklist

  • Reviewed the CONTRIBUTING.md guide (required)
  • Title matches the required conventional commits format, see here

Copy link
Collaborator

@JoaoBraveCoding JoaoBraveCoding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@JoaoBraveCoding
Copy link
Collaborator

JoaoBraveCoding commented Nov 27, 2024

I'm merging this since the warning referenced in #14817 (k8s-operatorhub/community-operators#5249 (comment)) are being generated by operator-sdk (https://github.com/k8s-operatorhub/community-operators/actions/runs/11720622623/job/32646420918#step:6:1275) which doesn't check for the version of the deprecated API see https://github.com/operator-framework/api/blob/master/pkg/validation/internal/removed_apis.go#L306

Created issue in validation tool operator-framework/api#378

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.

2 participants