Change:
</span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">effect</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;NoSchedule&#34;</span><span style="color:#bbb"> </span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">kubeletExtraArgs</span>:<span style="color:#bbb"> </span><span style="color:#bbb">    </span><span style="color:#000;font-weight:bold">v</span>:<span style="color:#bbb"> </span><span style="color:#099">4</span><span style="color:#bbb"> <del> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">ignorePreflightErrors</span>:<span style="color:#bbb"> </span><span style="color:#bbb"></span>- IsPrivilegedUser<span style="color:#bbb"> </span><span style="color:#bbb">   </span><span style="color:#000;font-weight:bold">imagePullPolicy</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;IfNotPresent&#34;</span><span style="color:#bbb"> </del> <ins> </span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">ignorePreflightErrors</span>:<span style="color:#bbb"> </span><span style="color:#bbb">    </span>- IsPrivilegedUser<span style="color:#bbb"> </span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">imagePullPolicy</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;IfNotPresent&#34;</span><span style="color:#bbb"> </ins> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">localAPIEndpoint</span>:<span style="color:#bbb"> </span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">advertiseAddress</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;10.100.0.1&#34;</span><span style="color:#bbb"> </span><span style="color:#bbb">  </span><span style="color:#000;font-weight:bold">bindPort</span>:<span style="color:#bbb"> </span><span style="color:#099">6443</span><span style="color:#bbb"> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">certificateKey</span>:<span style="color:#bbb"> </span><span style="color:#d14">&#34;e6a2eb8581237ab72a4f494f30285ec12a9694d750b9785706a83bfcbbbd2204&#34;</span><span style="color:#bbb"> <del> </span><span style="color:#bbb"> </span><span style="color:#000;font-weight:bold">skipPhases</span>:<span style="color:#bbb"> </span><span style="color:#bbb"> </span>- addon/kube-proxy<span style="color:#bbb"> </del> <ins> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">skipPhases</span>:<span style="color:#bbb"> </span><span style="color:#bbb">  </span>- addon/kube-proxy<span style="color:#bbb"> </ins> </span><span style="color:#bbb"></span>---<span style="color:#bbb"> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">apiVersion</span>:<span style="color:#bbb"> </span>kubeadm.k8s.io/v1beta3<span style="color:#bbb"> </span><span style="color:#bbb"></span><span style="color:#000;font-weight:bold">kind</span>:<span style="color:#bbb"> </span>ClusterConfiguration<span style="color:#bbb">

Discussion:
file: kubeadm- ignorePreflightErrors need to under nodeRegistration.
That is exactly what the reference is saying.
I think you're suggesting a clarification to Have I got that right?
In the example:
Hi I'm going to edit your follow-up for readability - to make the YAML formatting more obvious.
That YAML from the email message is equivalent to:
It looks like the rest of your follow-up message is missing I can see the start of a sentence, “In the example:”, but not the remainder. /triage needs-information.
The label(s) cannot be applied, because the repository doesn't have them. <detailsIn response to : It looks like the rest of your follow-up message is missing I can see the start of a sentence, “In the example:”, but not the remainder. Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage needs-information
Okay, that makes sense. The example might be wrong. I'll look into it.
/sig cluster-lifecycle
looks like both and have some minor indentation issues. i though that we fixed these (apparently not). i can send PR for k/k later today.
PR for k/k is here:
/triage accepted /kind bug /remove-triage needs-information
/assign Reference is being regenerated using the updated doc comments.