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
CEL cost budgeting inconsistent rejections #111769
Comments
but after I removed |
Looks like there the case where this happens is fairly specific. When a function that returns a single scalar result (e.g. @DangerOnTheRanger is working on a fix. Impacted use cases are comparison operator ( |
Should be fixed by google/cel-go#571. |
is this a blocker for 1.25? |
I don't think we should block 1.25 on this one. The practical situations are can happen are specific enough that I don't think waiting one more patch release is a big deal. We can fix in 1.25.1 and then backport (in cel-go we are going to backport the fix to the cel-go versions used by 1.24 and 1.23). |
What happened?
I attempted to apply the following CRDs to kubernetes local cluster running from rev 759785e
stable.example.com_mapimmutablekeys.yaml
stable.example.com_mapappendonlykeys.yaml
Applying the CRDs:
Diff of two CRDs for convenience (red is nonworking, green is working):
What did you expect to happen?
I expected both CRDs to be accepted by the apiserver.
How can we reproduce it (as minimally and precisely as possible)?
Apply the two CRDs from above.
Anything else we need to know?
/sig api-machinery
/triage accepted
/assign @DangerOnTheRanger
Kubernetes version
Cloud provider
N/A
OS version
No response
Install tools
No response
Container runtime (CRI) and version (if applicable)
No response
Related plugins (CNI, CSI, ...) and versions (if applicable)
No response
The text was updated successfully, but these errors were encountered: