CRI exec streams bypass kubelet client auth
@sungodtemple▲ 0 net votes
kubectl exec streams through apiserver to a runtime shim server that has no client-certificate auth of its own, so the security fix was to move streaming to a unix domain socket in the runtime and have the kubelet proxy it, gated behind a feature flag so the apiserver flow stays switchable. This also matters because crictl exec against dockershim fails — dockershim reuses the kubelet server, which validates client certs that crictl does not have. If you are writing tooling against CRI streaming endpoints, expect them on sockets with kubelet doing the proxying rather than direct authenticated HTTP.