Karl Stoney

Associated: https://github.com/kubernetes/kubernetes/issues/25908

For those who are interested, we worked around this by adding a livenessProbe to the sidecar injector for istio-proxy: ``` livenessProbe: exec: command: - /usr/local/bin/liveness.sh initialDelaySeconds: 3 periodSeconds: 10 failureThreshold:...

I use the auto sidecar injector. The probes are added to the injected template for the istio-proxy pod. Karl On Mon, 11 Feb 2019, 4:31 pm huikang @Stono thanks for...

Ohhh I get you. So in our CI pipeline we build our own istio-proxy image which pulls from the main image and copies these files in. We then use that...

@liamawhite do you know of any way to make istio-proxy exit with a 0 status code, at the moment if i send a `SIGTERM` I get 137, which causes a...

Seems to be fine for me in 1.1.1

We have started doing this recently btw folks in our pod spec: ``` command: ["/bin/bash", "-c"] args: - | trap "curl --max-time 2 -s -f -XPOST http://127.0.0.1:15000/quitquitquit" EXIT while !...

Yeah so we also have a liveness probe that looks for 15000 listening and if it's missing exits. It's hacky. On Tue, 30 Apr 2019, 11:33 am Mike Simons, wrote:...

https://github.com/kubernetes/enhancements/issues/753 Fyi In the interim I do think a simple controller watching jobs/pods/containers and then terminating istio proxy is the most pragmatic implementation. We have a lot of work loads...

BTW https://github.com/istio/istio/issues/20069 would also help with cronjobs