mirror of
https://github.com/kubernetes/kubernetes.git
synced 2026-07-15 20:53:45 -04:00
3bd2928d66
* pkg/apis/core: allow unsigned 32-bit Linux UIDs Signed-off-by: Kunalbehbud <121988281+Kunalbehbud@users.noreply.github.com> * apimachinery: fix UID validation on 32-bit platforms Format UID validation range errors with int64 bounds so accepting Linux UIDs up to MaxUint32 does not overflow int on 32-bit typecheck targets. Signed-off-by: Kunalbehbud <121988281+Kunalbehbud@users.noreply.github.com> * pkg/apis/core: limit uint32 UID validation to pod status Keep pod spec and kubelet image user validation on the existing int32 UID range, and only accept the full Linux uint32 UID range for container status user fields. Signed-off-by: Kunalbehbud <121988281+Kunalbehbud@users.noreply.github.com> * pkg/apis/core: inline container status UID range check Per review, inline the uint32 UID range check directly in validateLinuxContainerUser and drop the generic-sounding isValidLinuxContainerUserID helper (and its constants), so the range that is wider than runAsUser can only ever be applied to container status validation. * pkg/apis/core: inline linux user validation into validateContainerStatusUsers Per review, inline the linux container-user checks directly into validateContainerStatusUsers and remove the validateLinuxContainerUser helper, so nothing other than container status validation can reach the wider-than-runAsUser UID range. --------- Signed-off-by: Kunalbehbud <121988281+Kunalbehbud@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| fuzzer | ||
| helper | ||
| install | ||
| pods | ||
| v1 | ||
| validation | ||
| annotation_key_constants.go | ||
| doc.go | ||
| json.go | ||
| objectreference.go | ||
| OWNERS | ||
| register.go | ||
| resource.go | ||
| taint.go | ||
| taint_test.go | ||
| toleration.go | ||
| toleration_test.go | ||
| types.go | ||
| types_test.go | ||
| zz_generated.deepcopy.go | ||