Open romilbhardwaj opened 1 week ago
I noticed a bunch of kubectl port-forward commands left over on my machine even though I do no have any k8s clusters running:
kubectl port-forward
(base) ➜ ~ ps -ax | grep kubectl 84551 ?? 0:09.81 kubectl --context=kind-skypilot --namespace=default port-forward pod/test-2ea4-head :22 28531 ttys001 0:03.67 kubectl --context=kind-skypilot --namespace=default port-forward pod/test-2ea4-head :22 28550 ttys001 0:03.72 kubectl --context=kind-skypilot --namespace=default port-forward pod/test-2ea4-head :22
Same was also reported by user. Perhaps our SSH proxy command is leaking these processes somehow.
I noticed a bunch of
kubectl port-forward
commands left over on my machine even though I do no have any k8s clusters running:Same was also reported by user. Perhaps our SSH proxy command is leaking these processes somehow.