Adrien Delorme 27f239dcf5 fix(ateompath): validate ateom socket path length (#92) ...

## Symptom

When `<namespace>:<pod-name>` exceeds 107 bytes, `ateom-gvisor` exits
with `bind: invalid argument` and the controller surfaces a generic
`DeadlineExceeded`.

## Cause

Linux limits unix-socket paths to 107 bytes (`sockaddr_un.sun_path`). A
pod's ReplicaSet hash can jiggle between 8 and 10 chars across rollouts,
so a demo that fits at 8 silently breaks at 10 with no clear error.

## Fix

Add `ValidateAteomSocketPath` (with unit tests) and call it from
`ateom-gvisor` before the bind, so the operator sees the real cause in
the pod log instead of a kernel EINVAL.

2026-05-27 18:58:47 -07:00

..

ateapi

…

atecontroller

…

atelet

…

atenet

…

ateom-gvisor

fix(ateompath): validate ateom socket path length (#92)

2026-05-27 18:58:47 -07:00

kubectl-ate

…

podcertcontroller

…