kubeadm API reference docs still mention "master" taint

[neolit123]

This is a Bug Report

Problem:

while cleaning up mentions of the legacy "master" taint in kubeadm docs:
#33834

saw the following:

~/go/src/k8s.io/website/content/en/docs$ grep "node-role.kubernetes.io/master" * -rnI
reference/config-api/kubeadm-config.v1beta2.md:1280:<code>'node-role.kubernetes.io/master=&quot;&quot;'</code>. If you don't want to taint your control-plane node,
reference/config-api/kubeadm-config.v1beta3.md:1267:<code>taints: [&quot;node-role.kubernetes.io/master:&quot;&quot;]</code>.

it seems the generated reference API docs for kubeadm still include the "master" taint.

Proposed Solution:

cleanup mentions of the old taint from kubeadm's API reference docs at k8s.io.

perhaps these need to be synced with:
https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/apis/kubeadm/v1beta2/doc.go
https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/apis/kubeadm/v1beta3/doc.go

for dev-1.25 and main at k/website

we removed the old taint from there before 1.24 was released.

Page to Update:

https://kubernetes.io/docs/reference/config-api/kubeadm-config.v1beta2/
https://kubernetes.io/docs/reference/config-api/kubeadm-config.v1beta3/

[k8s-ci-robot]

@neolit123: This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[neolit123]

/sig cluster-lifecycle
/priority important-soon
/kind cleanup

[neolit123]

cc @tengqm