You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d282010
Browse filesBrowse the repository at this point in the historyBrowse files
authored
fix(deploy): a restricted render probes natively; refuse what a native probe cannot express (#91)
A cell's execution admission refuses any container with an exec probe, and
model is down on it. Restricted renders (what a cell runs) now render the
kubelet's own handlers: a transport predicate is a tcpSocket probe, an HTTP
predicate an httpGet on the same path (HTTPS when the endpoint is secured),
with the authored timing kept. A predicate those handlers cannot express — a
response-body check, or a status outside the kubelet's 200–399 — is refused
at render, never weakened. The local apply keeps probe.py's exec probe.
Co-authored-by: Antoine Toussaint <toussaint.antoine@gmail.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
returnnil, fmt.Errorf("the Kubernetes manifest profile requires explicit endpoint health.startup and health.liveness; readiness is not a restart policy")
returnnil, fmt.Errorf("a cell refuses an exec probe, and a native HTTP probe cannot check that the response body contains %q; drop the body predicate or probe a path whose status alone answers", config.Body)
returnnil, fmt.Errorf("a cell refuses an exec probe, and a native HTTP probe takes only %d–%d as success, so it cannot accept %d–%d", kubeletSuccess[0], kubeletSuccess[1], status[0], status[1])
0 commit comments