<p>Here are the versions I'm using</p>

<p>Docker-ce</p>

<pre><code>Client:
 Version:           17.06.1-ce

Server:
 Engine:
  Version:          17.06.1-ce
</code></pre>

<p>minikube:</p>

<pre><code>kubectl 
</code></pre>

<p>Kubectl:</p>

<pre><code>Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:17:28Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
</code></pre>

<p>Kubeadm:</p>

<pre><code>kubeadm version: &amp;version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
</code></pre>

<p>VirtualBox:</p>

<pre><code>Version 5.2.18 r124319 (Qt5.6.2)
</code></pre>

<p>I happen to need to specify the following:</p>

<pre><code>kubeadm reset
kubeadm init --pod-network-cidr=192.168.0.0/16
</code></pre>

<p>However when I then start minikube it always fails with the following:</p>

<pre><code>kubeconfig file "/etc/kubernetes/admin.conf" exists already but has got the wrong CA cert
</code></pre>

<p>The workaround I've been able to find is to delete all <code>.conf</code> files in <code>/etc/kubernetes</code></p>

<pre><code>  cd /etc/kubernetes/
  sudo rm *.conf
  cd
  sudo minikube delete # may also need rm -rf ~/.minikube
  sudo minikube start --vm-driver=none
</code></pre>

<p>However new config files are generated and so are the .yaml files under `/etc/kubernetes/manifest' thus erasing all additional attributes of the configuration</p>

<p>Up to that point doing <code>kubeadm config view</code> would show the kube init <code>pod-network-cidr</code> parmameter but not after deleting the <code>.conf</code> files and starting minikube again</p>

<p>First:
Is this <code>...wrong CA cert</code> error a bug with minikube?</p>

<p>Is there an alternate workaround that would maintain the extra parameters passed during <code>kubeadm init</code>?</p>

<p>I've also tried to pass the following 3 attributes that get cleared from the <code>kube-controller-manager.yaml</code> file as <code>extra-config</code> parameters on the <code>minikube start</code> command</p>

<p>The three missing attributes associated with <code>--pod-network-cidr=192.168.0.0/16</code> that I've been able to ascertain are:</p>

<pre><code> --allocate-node-cidrs=true
 --cluster-cidr=192.168.0.0/16
 --node-cidr-mask-size=24
</code></pre>

<p>My mikikube start command looks like this:</p>

<pre><code>sudo minikube start --vm-driver=none --extra-config=controller-manager.allocate-node-cidrs=true, controller-manager.cluster-cidr=192.168.0.0/16, controller-manager.node-cidr-mask-size=24
</code></pre>

<p>But I get further error when trying this</p>

<p>Any suggestions?</p>

Gilles Depatie
<ul>
<li>You generally use minikube to setup a mini kubernetes cluster of its own. Generally on your local machine.</li>
<li>You generally use kubeadm to setup a full blown cluster of its own.</li>
<li>You don't generally use both of them together.</li>
</ul>

<p>Hope it helps!</p>
