Hacker News Reader

TLDR: Introduce a restartPolicy field to init containers and use it to indicate that an init container is a sidecar container. Kubelet will start init containers with restartPolicy=Always in the order with other init containers, but instead of waiting for its completion, it will wait for the container startup completion.

View on HN

Hopefully these changes should make Envoy sidecars (and sidecar co-existence in general) more reliable.

What's the use-case for Envoy as a sidecar? (As someone using Envoy Gateway.)

Service mesh. Istio for example injects an envoy sidecar to each pod, and manages everything "meshy" (routing, retries, mTLS, etc) via this sidecar.

This is also how linkerd works, though they're using their own purpose-built sidecar rather than envoy.

Isn’t the new ambient mesh available in istio 1.18 sidecar-less?

Yep, it’s also alpha, under intense development, and by every account (including those vendors who are chomping at the bit to start selling it to customers) absolutely not production ready.

Oh, good to know. I was about to pack a spike into an upcoming sprint.

It seems like there could be a better marker for this. Maybe my skill with Kubernetes is too low for it to make sense.

Reply on news.ycombinator.com