<p>I'm following a Kubernetes tutorial, and cannot run first command (<code>minikube start --vm-driver=hyperkit</code>). I'm using a MacBook Pro Intel on macOs Monterey. I cannot make it work because of TLS error.</p>
<pre><code>$ minikube start --vm-driver=hyperkit
😄  minikube v1.25.2 on Darwin 12.2.1
🆕  Kubernetes 1.23.3 is now available. If you would like to upgrade, specify: --kubernetes-version=v1.23.3
✨  Using the hyperkit driver based on existing profile
👍  Starting control plane node minikube in cluster minikube
🔄  Restarting existing hyperkit VM for &quot;minikube&quot; ...
🐳  Preparing Kubernetes v1.20.2 on Docker 20.10.3 ...
❌  Problems detected in etcd [592b8a58065e]:
    2022-03-19 22:12:03.193985 I | embed: rejected connection from &quot;127.0.0.1:38132&quot; (error &quot;remote error: tls: bad certificate&quot;, ServerName &quot;&quot;)
</code></pre>
<p>I tried :</p>
<ol>
<li>Restarted the computer : <a href="https://github.com/kubernetes/minikube/issues/4329" rel="noreferrer">https://github.com/kubernetes/minikube/issues/4329</a></li>
<li>Used <code>--embed-certs</code> argument</li>
</ol>
<pre class="lang-sh prettyprint-override"><code>$ minikube start --vm-driver=hyperkit --embed-certs
😄  minikube v1.25.2 on Darwin 12.2.1
🆕  Kubernetes 1.23.3 is now available. If you would like to upgrade, specify: --kubernetes-version=v1.23.3
✨  Using the hyperkit driver based on existing profile
👍  Starting control plane node minikube in cluster minikube
🔄  Restarting existing hyperkit VM for &quot;minikube&quot; ...
🐳  Preparing Kubernetes v1.20.2 on Docker 20.10.3 ...
❌  Problems detected in etcd [78d1e36569b8]:
    2022-03-19 22:20:53.503532 I | embed: rejected connection from &quot;127.0.0.1:34926&quot; (error &quot;remote error: tls: bad certificate&quot;, ServerName &quot;&quot;)
</code></pre>
<p>I'm new to K8s, what could cause such behaviour ?</p>
<hr />
<p>I installed minikube and hyperkit with homebrew. When I display the kubectl version I get another connection error :</p>
<pre class="lang-sh prettyprint-override"><code>kubectl version
Client Version: version.Info{Major:&quot;1&quot;, Minor:&quot;22&quot;, GitVersion:&quot;v1.22.5&quot;, GitCommit:&quot;5c99e2ac2ff9a3c549d9ca665e7bc05a3e18f07e&quot;, GitTreeState:&quot;clean&quot;, BuildDate:&quot;2021-12-16T08:38:33Z&quot;, GoVersion:&quot;go1.16.12&quot;, Compiler:&quot;gc&quot;, Platform:&quot;darwin/amd64&quot;}
Unable to connect to the server: dial tcp 192.168.64.2:8443: i/o timeout
</code></pre>

<p>The <code>kubectl version</code> error helped :
<a href="https://stackoverflow.com/questions/49260135/unable-to-connect-to-the-server-dial-tcp-i-o-time-out">Unable to connect to the server: dial tcp i/o time out</a></p>
<p>It seems I had already played with k8s :</p>
<pre class="lang-sh prettyprint-override"><code>$ kubectl config view
apiVersion: v1
clusters:
- cluster:
    certificate-authority: /Users/xxx/.minikube/ca.crt
    extensions:
    - extension:
        last-update: Sat, 13 Mar 2021 13:40:06 CET
        provider: minikube.sigs.k8s.io
        version: v1.18.1
      name: cluster_info
    server: https://192.168.64.2:8443
  name: minikube
contexts:
- context:
    cluster: minikube
    extensions:
    - extension:
        last-update: Sat, 13 Mar 2021 13:40:06 CET
        provider: minikube.sigs.k8s.io
        version: v1.18.1
      name: context_info
    namespace: default
    user: minikube
  name: minikube
current-context: minikube
kind: Config
preferences: {}
users:
- name: minikube
  user:
    client-certificate: /Users/xxx/.minikube/profiles/minikube/client.crt
    client-key: /Users/xxx/.minikube/profiles/minikube/client.key

</code></pre>
<p>First I deleted the existing cluster :</p>
<pre><code>$ kubectl config delete-cluster minikube
deleted cluster minikube from /Users/xxx/.kube/config
</code></pre>
<p>Then run</p>
<pre class="lang-sh prettyprint-override"><code>$ minikube delete
🔥  Deleting &quot;minikube&quot; in hyperkit ...
💀  Removed all traces of the &quot;minikube&quot; cluster.
</code></pre>
<p>Finally :</p>
<pre class="lang-sh prettyprint-override"><code>$ minikube start --vm-driver=hyperkit
😄  minikube v1.25.2 on Darwin 12.2.1
✨  Using the hyperkit driver based on user configuration
👍  Starting control plane node minikube in cluster minikube
💾  Downloading Kubernetes v1.23.3 preload ...
    &gt; preloaded-images-k8s-v17-v1...: 505.68 MiB / 505.68 MiB  100.00% 923.34 K
🔥  Creating hyperkit VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
🐳  Preparing Kubernetes v1.23.3 on Docker 20.10.12 ...
    ▪ kubelet.housekeeping-interval=5m
    ▪ Generating certificates and keys ...
    ▪ Booting up control plane ...
    ▪ Configuring RBAC rules ...
🔎  Verifying Kubernetes components...
    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🌟  Enabled addons: default-storageclass, storage-provisioner
🏄  Done! kubectl is now configured to use &quot;minikube&quot; cluster and &quot;default&quot; namespace by default
</code></pre>
