track/close kubelet->API connections on heartbeat failure #63492
we're already typically tracking kubelet -> API connections and have the ability to force close them as part of client cert rotation. if we do that tracking unconditionally, we gain the ability to also force close connections on heartbeat failure as well. it's a big hammer (means reestablishing pod watches, etc), but so is having all your pods evicted because you didn't heartbeat.
this intentionally does minimal refactoring/extraction of the cert connection tracking transport in case we want to backport this
The text was updated successfully, but these errors were encountered:
green serial run containing this PR:
many green slow suite CI runs containing this PR, e.g.:
scale test showed no regressions (https://k8s-testgrid.appspot.com/sig-release-master-blocking#gce-scale-performance, run 154)