Kubernetes 1.38 CRD CEL Validation Rules Failing After cel-go Upgrade
Is it fixed? Not yet.
Ongoing since Nov 13, 18:39 UTC. First reported Nov 13, 18:39 UTC.
What happened
Kubernetes 1.38 rejects CustomResourceDefinitions with CEL validation rules that index the result of split() and call linear-cost string functions like .matches() due to a cel-go v0.33.0 upgrade that spikes estimated expression costs. Users attempting to apply or evaluate these CRDs experience validation failures.
What caused it?
An upgrade to cel-go v0.33.0 in Kubernetes 1.38 increased the estimated cost of certain CEL validation rules, such as indexing split() results and calling linear-cost string functions, causing them to exceed limits.
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on GitHub issue
CRD CEL validation rules that use `split()` fail in 1.38 after `cel-go` v0.33.0 upgrade
Source
Evidence
1 report · 1 GitHubShow
- [1]GitHub First reportCRD CEL validation rules that use `split()` fail in 1.38 after `cel-go` v0.33.0 upgrade(opens GitHub issue in a new tab)
What happened? After the cel-go v0.33.0 upgrade in #143439 (4ce108bf643), kube-apiserver in Kubernetes 1.38 rejects CustomResourceDefinitions whose x-kubernetes-validations rules index the result of split() and call a linear-cost string function such as .matches() on the indexed element (for example, self.key.split('/')[1].matches('^A-Za-z0-9?$')). In Kubernetes 1.37 (cel-go v0.32), the rule above has an estimated cost of 629,159. In Kubernetes 1.38 (cel-go v0.33.0), its estimated cost…
by ajaysundark 0upvotes 2comments
FAQ
What happened in the Kubernetes outage?
Kubernetes 1.38 rejects CustomResourceDefinitions with CEL validation rules that index the result of split() and call linear-cost string functions like .matches() due to a cel-go v0.33.0 upgrade that spikes estimated expression costs. Users attempting to apply or evaluate these CRDs experience validation failures.
What is affected by the Kubernetes outage?
Kubernetes (versions: 1.38).
When did the Kubernetes outage start and end?
It started Nov 13, 18:39 UTC and is still ongoing (5 d 10 h so far). This page updates as it develops.
How do I get alerts for Kubernetes?
Subscribe to the Kubernetes RSS feed for every new Kubernetes incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Kubernetes is down. Kubernetes feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.