You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Software version numbers
State the version numbers of applications involved in the bug.
Kubernetes version: 1.19
Kyverno version: 1.3.5
Describe the bug
When using the recommended safe-to-evict policy from the docs, it fails to properly validate on cronjobs that do not have a volume present
To Reproduce
Steps to reproduce the behavior:
Create cronjob manifest without a volume definition:
@kacejot - are you planning to take this issue? Is this the same issue as what we have in #1658? If so, I can re-assign this issue to you and let's close both issues with fixing PR.
Software version numbers
State the version numbers of applications involved in the bug.
Describe the bug
When using the recommended
safe-to-evict
policy from the docs, it fails to properly validate on cronjobs that do not have a volume presentTo Reproduce
Steps to reproduce the behavior:
Expected behavior
The policy applies the annotation if an emptydir or host path is present, or passes without error if not.
You can get it to work by changing the policy mutate spec from:
to
Opening per request of @realshuting in kyverno/policies#61
The text was updated successfully, but these errors were encountered: