e97531b349
The generated ResourceClaim name and the names of the ResourceClaimTemplate and ResourceClaim referenced by a pod must be valid according to the resource API, otherwise the pod cannot start. Checking this was removed from the original implementation out of concerns about validating fields in core against limitations imposed by a separate, alpha API. But as this was pointed out again in https://github.com/kubernetes/kubernetes/pull/116254#discussion_r1134010324 it gets added back. The same strings that worked before still work now. In particular, the constraints for a spec.resourceClaim.name are still the same (DNS label). |
||
|---|---|---|
| .. | ||
| fuzzer | ||
| install | ||
| v1alpha2 | ||
| validation | ||
| doc.go | ||
| OWNERS | ||
| register.go | ||
| types.go | ||
| zz_generated.deepcopy.go | ||