kyverno: bump to v1.15.2 on staging #8216
Conversation
🤖 Gemini AI Assistant AvailableHi @sadlerap! I'm here to help with your pull request. You can interact with me using the following commands: Available Commands
How to Use
PermissionsOnly OWNER, MEMBER, or COLLABORATOR users can trigger my responses. This ensures secure and appropriate usage. This message was automatically added to help you get started with the Gemini AI assistant. Feel free to delete this comment if you don't need assistance. |
|
🤖 Hi @sadlerap, I've received your request, and I'm working on it now! You can track my progress in the logs for more details. |
|
/hold Investigating kube-linter failures, was expecting to potentially see issues from it. |
sadlerap
force-pushed
the
kyverno-1.15-staging
branch
from
60d32c5 to
dcfb0ee
Compare
sadlerap
force-pushed
the
kyverno-1.15-staging
branch
from
dcfb0ee to
7b3985b
Compare
sadlerap
force-pushed
the
kyverno-1.15-staging
branch
2 times, most recently
from
c8d67fa to
7b55f43
Compare
sadlerap
force-pushed
the
kyverno-1.15-staging
branch
3 times, most recently
from
30be6d9 to
09872be
Compare
Upgrade kyverno from v1.13.4 to v1.15.2 on the staging clusters. Part-of: KFLUXINFRA-1963 Signed-off-by: Andy Sadler <[email protected]>
sadlerap
force-pushed
the
kyverno-1.15-staging
branch
from
09872be to
edfc6ee
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hugares, sadlerap The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/unhold Ready for review. |
Upgrade kyverno from v1.13.4 to v1.15.2 on the staging clusters.
The PodDisruptionBudgets were having a hard time passing
kube-linterchecks (kube-linter wasn't happy with theminAvailablefield), so modifications were needed to ensure they pass without issue.