<p>I am trying to add livenessprobe for <a href="https://github.com/kubernetes-csi/external-snapshotter/tree/v6.0.1" rel="nofollow noreferrer">snapshot-controller</a>. snapshot-controller deployment mentioned <a href="https://github.com/kubernetes-csi/external-snapshotter/blob/v6.0.1/deploy/kubernetes/snapshot-controller/setup-snapshot-controller.yaml" rel="nofollow noreferrer">here</a> to be specific. I tried to exec into controller pod to see what can be used for liveness probe. But not able to get into the pod. Has someone tried adding probes for snapshot-controller.</p>

<p>In the github repository you shared: <a href="https://github.com/kubernetes-csi/external-snapshotter/tree/v6.0.1#snapshot-controller-command-line-options" rel="nofollow noreferrer">https://github.com/kubernetes-csi/external-snapshotter/tree/v6.0.1#snapshot-controller-command-line-options</a></p>
<h4>Important optional arguments that are highly recommended to be used</h4>
<blockquote>
<p>--http-endpoint: The TCP network address where the HTTP server for diagnostics, including metrics and leader election health check, will listen (example: :8080 which corresponds to port 8080 on local host). The default is empty string, which means the server is disabled.</p>
</blockquote>
<p>You should be able to use this, if you do enable this option. At which point, you could query port 8080, path /metrics for example.</p>
<p>Note: if you need to troubleshoot something like this and do not have a shell in your container image. You could use <code>kubectl debug</code>, see: <a href="https://kubernetes.io/docs/tasks/debug/debug-application/debug-running-pod/#debugging-using-a-copy-of-the-pod" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/debug/debug-application/debug-running-pod/#debugging-using-a-copy-of-the-pod</a></p>
