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
[BUG] CRDs are only loaded on startup and not refreshed #2094
Comments
Thanks @MarcelMue, we'll investigate this issue and get back. |
@realshuting Has there been progress on this issue? We run into problems when we add new CRDs currently. |
No I wasn't able to work on this, will look into it tomorrow and get back to you. |
Hi @MarcelMue - looks like the issue was resolved in the latest main, you can verify with image tag
|
BTW, if tag
I'm closing this issue for now. Let me know if it does not work for you. |
Thanks for the heads up - will test this :) |
Software version numbers
State the version numbers of applications involved in the bug.
Describe the bug
Add CRD and mutation policy on this CRD while Kyverno is running -> policy always fails until Kyverno pod is restarted
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The mutation policy should work and no errors should be emitted.
Additional context
The error log which happens:
After this log, the mutation rule is not triggered.
Restarting the kyverno pod leads to the expected behavior.
Resources for easy reproduction
CRD: https://raw.githubusercontent.com/kubernetes-sigs/cluster-api-provider-aws/main/config/crd/bases/infrastructure.cluster.x-k8s.io_awsclusterroleidentities.yaml
CR to apply:
Rule:
The text was updated successfully, but these errors were encountered: