mirror of
https://github.com/k3s-io/kubernetes.git
synced 2026-07-17 20:00:07 +00:00
The spec is the same in both, so those fields are now handled by common code. For ResourceClaim spec updates, the "in use" check now only considers the spec. Theoretically some features could be in use in an old ResourceClaim status and not in use in the spec. This can only occur in a spec update, which is currently prevented because the entire spec is immutable. Even if it was allowed, preventing adding disabled fields to the spec is the right thing to do regardless of what may have ended up in the status earlier.