Repository navigation
[release-v1.44] Render a write-only tiered policy passthrough in v3 CRD mode - #5266
Merged
caseydavenport merged 3 commits intoAug 27, 2026
Conversation
The IPPool CEL validation rules exceed the CRD cost budget on 1.31.
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.
Cherry-pick of #5259 to
release-v1.44.The tiered policy passthrough role is only rendered when running the aggregation API server, so on clusters serving the Calico v3 API through CRDs every tier-scoped role is denied on all verbs. This renders it in both modes: all verbs under the aggregation API server as before, writes only in v3 CRD mode, where writes reach the tiered policy admission webhook and reads stay subject to ordinary RBAC. Staged policies also move into the base role, since they are tiered in Calico as well as Enterprise.
The second commit syncs the Calico and Enterprise CRDs. The generated-file check was already failing on this branch before the pick, since the tracked Calico and Enterprise branches have added CRD fields since the last sync.
The third commit moves the FV kind cluster to Kubernetes 1.32. The new IPPool validation rules exceed the CRD cost budget on 1.31, so the synced CRDs cannot be applied there at all.