feat: add UseServerSideApply to GeneratingPolicySpec #43
+18
−0
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.
What this PR does
This PR adds a new optional field,
spec.useServerSideApply, to GeneratingPolicy (and NamespacedGeneratingPolicy) specs.This brings GeneratingPolicy in line with existing behavior in
ClusterPolicy/Policy, where users can choose between:Why this is needed
Currently:
useServerSideApplyexists for generate rules inClusterPolicy/PolicyThis is limiting for users running:
This gap is tracked in Issue [(https://github.com/kyverno/kyverno/issues/14853)].
What changed
Added
UseServerSideApplyfield to:GeneratingPolicySpecField is optional and defaults to
falseIncludes comments and JSON tags consistent with existing API patterns
CRDs regenerated accordingly
How this relates to the Kyverno implementation
This PR only defines the API contract.
A follow-up PR in the main
kyverno/kyvernorepository:reads this field from the policy spec
passes it through the CEL engine and controllers
switches resource creation/update logic between:
CreateResource/UpdateResourceApplyResourcewhen SSA is enabledKeeping the API change separate makes the review smaller and cleaner, and avoids mixing API evolution with controller logic.
Backward compatibility
Related issue