-
Notifications
You must be signed in to change notification settings - Fork 20
Feature: allow user to specify the priorityClassName for PolicyServer #1335
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
Conversation
4b070eb to
3a2d102
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good to me, but it's necessary to double check the failing tests
|
Please rebase to use current tests, PR is based on code from April. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please let's not mix up requirements. |
Ok, then please add label so priority class is not under replicas. |
|
@kravciak for the records: Rancher head breaks when I create it with Docker so I cannot reproduce eventual new BE issues created between the moment of the PR and my absence. We need to reproduce your issue in order to address that. Clearable functionality seems to be broken on dashboard and I filed a separated issue for it. API of the component will be inherited on version bump. |
6a3c7af to
ee0b7e3
Compare
|
After doing rebase of Kubewarden, I still do not encounter any issue. Kapture.2025-11-03.at.17.34.24.mp4 |
|
I just realized to have been pushing to the rancher remote, so I created a new PR: #1348 |


Description
Fixes #1184
Added unit test and launcher options for VSCode.
Test
/c/local/kubewarden/policies.kubewarden.io.policyserver/create#generalPriority Class NameVideo
Kapture.2025-10-24.at.18.14.40.mp4