Laurent Demailly

Unfortunately 5 minutes is too long for when using spot /remove-lifecycle stale

I will comment with more details when time permits but note you can reduce de-registration to around 45s (from over 3 minutes) using http(s) instead of tcp healthchecks. which help...

@roimor ```yaml serviceAnnotations: service.beta.kubernetes.io/aws-load-balancer-type: "nlb-ip" service.beta.kubernetes.io/aws-load-balancer-ssl-ports: https service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: "*" service.beta.kubernetes.io/aws-load-balancer-healthcheck-protocol: HTTPS service.beta.kubernetes.io/aws-load-balancer-healthcheck-port: "8443" service.beta.kubernetes.io/aws-load-balancer-healthcheck-path: /ready ``` combined with, istio/envoy wise: ```yaml containers: - name: istio-proxy lifecycle: preStop: exec: command: -...

subscribing as we have a similar issue but killing stunnel doesn't fix it for us still Jun 7 01:00:38 [ip] kernel: nfs: server 127.0.0.1 not responding, timed out is there...

edit: killing these 2 processes (ps btw was hanging too!) ``` root 18314 0.0 0.0 717228 13624 ? Ssl May25 3:21 /bin/aws-efs-csi-driver --endpoint=unix:///var/lib/csi/sockets/pluginproxy/csi.sock --logtostderr --v=2 --delete-access-point-root-dir=false --vol-metrics-opt-in=false root 20172 0.0...

fix in https://github.com/golang/go/issues/52882

another shameless plug: https://github.com/istio/fortio like curl supports (multiple) -H flags to add multiple extra headers to the http requests

shameless plug: https://github.com/istio/fortio also had issues on windows at first but should now work fine after eliminating trying to send signal to self

which version? can you give exact repro steps?

I can reproduce the problem, which is due to asking for large payload: ``` $ fortio load -qps 100 -t 10s "http://localhost:8080/?size=131072:50,65536:25,32768:25" Fortio 1.34.1 running at 100 queries per second,...