Update Kyverno chart version from 3.2.5 to 3.4.4#333
Merged
Conversation
Updated to address new Bitnami image restrictions where images are now only available under the latest tag. Version 3.4.4 includes the updated image references (reg.kyverno.io) compatible with these restrictions while maintaining compatibility with Kubernetes 1.26 (no ValidatingAdmissionPolicy requirement).
evgheni7
approved these changes
Oct 1, 2025
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updated Kyverno chart version from 3.2.5 to 3.4.4 to address Bitnami image registry restrictions while maintaining Kubernetes 1.26 compatibility.
Motivation
Bitnami container images are now only available under the
latesttag, causing Kyverno 3.2.5 to fail when pulling images. The updated version usesreg.kyverno.ioas the defaultregistry, resolving this issue.
Changes
kyvernoChartVersionininternal/policy/kyverno.gofrom "3.2.5" to "3.4.4"Why 3.4.4 Instead of 3.5.2?
reg.kyverno.iodefault registryValidatingAdmissionPolicyCRD (K8s 1.30+ feature)Testing
Breaking Changes
None. Maintains backward compatibility within Kyverno 3.x series.