<p>I've just enabled docker desktop's kubernetes feature on my m2 macbook air, and I observed that the <code>vpnkit-controller</code> pod under <code>kube-system</code> namespace has restarted several times since enabling the feature, is this normal or I missed some of the settings?</p>
<p><a href="https://i.stack.imgur.com/HnGmH.png" rel="nofollow noreferrer">screen shot of pod status</a></p>

<h2>Update:</h2>
<p>This problem was resolved after upgrading Docker-Desktop to version <code>4.20.1</code></p>
<p>which uses a new <code>docker/desktop-vpnkit-controller</code> image tagged with <code>dc331cb22850be0cdd97c84a9cfecaf44a1afb6e</code></p>
<hr />
<h2>Original Answer</h2>
<p>you can get the log of crashed <code>vpnkit-controller</code> pod via command as follow:</p>
<pre class="lang-bash prettyprint-override"><code>kubectl logs -p -n kube-system vpnkit-controller
</code></pre>
<p>this shows me as follows</p>
<pre><code>2023/03/09 03:45:54 Starting kube-vpnkit-forwarder...
W0309 04:03:37.888472       1 reflector.go:334] github.com/moby/vpnkit/go/cmd/kube-vpnkit-forwarder/main.go:49: watch of *v1.Service ended with: The resourceVersion for the provided watch is too old.
log: exiting because of error: log: cannot create log: open /tmp/kube-vpnkit-forwarder.vpnkit-controller.unknownuser.log.WARNING.20230309-040337.1: no such file or directory
</code></pre>
