<p dir="auto"><strong>Is this a request for help?</strong> (If yes, you should use our troubleshooting guide and community support channels, see <a href="http://kubernetes.io/docs/troubleshooting/" rel="nofollow">http://kubernetes.io/docs/troubleshooting/</a>.): No</p>
<p dir="auto"><strong>What keywords did you search in Kubernetes issues before filing this one?</strong> (If you have found any duplicates, you should instead reply there.): kubeadm defaults</p>
<hr>
<p dir="auto"><strong>Is this a BUG REPORT or FEATURE REQUEST?</strong> (choose one):<br>
BUG REPORT</p>

<p dir="auto"><strong>Kubernetes version</strong> (use <code class="notranslate">kubectl version</code>):<br>
v1.4.3</p>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>: N/A</li>
<li><strong>OS</strong> (e.g. from /etc/os-release): N/A</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>): N/A</li>
<li><strong>Install tools</strong>: kubeadm</li>
<li><strong>Others</strong>: N/A</li>
</ul>
<p dir="auto"><strong>What happened</strong>:<br>
Using <code class="notranslate">kubeadm init --config /path/to/config.yml</code> appears to block default values from being set. I first noticed it where a pre-flight check of the Servicer CIDR was presenting itself as an empty string although I had not set it through the command line flag nor in the config file. I also noticed that kubelet requests to the API server were being sent to port 0 as the API server default port had not been set.</p>
<p dir="auto"><strong>What you expected to happen</strong>:<br>
A config file should only override defaults, not make it so that no defaults are set.</p>
<p dir="auto"><strong>How to reproduce it</strong> (as minimally and precisely as possible):<br>
Use <code class="notranslate">kubeadm init --config /path/to/config.yml</code> with an appropriate configuration file that does not set the service CIDR, for example, and note that pre-flight checks will fail due to the default values not being set.</p>
<p dir="auto"><strong>Anything else do we need to know</strong>:<br>
A temporary workaround is to explicitly set all values to their defaults or the value you desire.</p>
<p dir="auto">Compilation error in pkg/util/mount/mount_unsupported.go. GetDeviceNameFromMount declared twice. <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="171543127" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/30724" data-hovercard-type="pull_request" data-hovercard-url="/kubernetes/kubernetes/pull/30724/hovercard" href="https://github.com/kubernetes/kubernetes/pull/30724">#30724</a> and <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="171293778" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/30666" data-hovercard-type="pull_request" data-hovercard-url="/kubernetes/kubernetes/pull/30666/hovercard" href="https://github.com/kubernetes/kubernetes/pull/30666">#30666</a> are duplicates and one of them need to be reverted. (build is disabled for linux, that's why both of them got in)</p>