kubeadm: add missing RBAC for getting nodes on "upgrade apply"

[neolit123]

What this PR does / why we need it:

b117a92 added a new check during "join" whether a Node with
the same name exists in the cluster.

When upgrading from 1.17 to 1.18 make sure the required RBAC
by this check is added. Otherwise "kubeadm join" will complain that
it lacks permissions to GET a Node.

Which issue(s) this PR fixes:

Refs kubernetes/kubeadm#2079

Special notes for your reviewer:
NONE

Does this PR introduce a user-facing change?:

kubeadm: fix a bug where post upgrade to 1.18.x, nodes cannot join the cluster due to missing RBAC

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/assign @rosti @randomvariable
/priority critical-urgent
/kind bug

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neolit123

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• cmd/kubeadm/OWNERS [neolit123]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[neolit123]

@kubernetes/sig-cluster-lifecycle-pr-reviews

[randomvariable]

/lgtm

[neolit123]

/retest

[fejta-bot]

/retest
This bot automatically retries jobs that failed/flaked on approved PRs (send feedback to fejta).

Review the full test history for this PR.

Silence the bot with an /lgtm cancel or /hold comment for consistent failures.

[yogeek]

Hello @neolit123

Thanks for this fix. We just had the issue in our 1.17 => 1.18 upgrade : is the fix only for 1.19 kubeadm version (I see "1.19 milestone") or can it be backport to previous versions too please ?

[neolit123]

@yogeek

there is no need for this to be backported to earlier versions.

this current PR was for 1.19.

this was the cherry pick for 1.18, so the fix should be in the latest 1.18.x PATCH version:
#89577

[yogeek]

@neolit123 oh ok. In our case, we faced the issue when using kubeadm 1.18 to upgrade a 1.17 cluster to 1.18 so you say it is normal because the fix was in 1.18 and 1.19 right ?

[neolit123]

@neolit123 oh ok. In our case, we faced the issue when using kubeadm 1.18 to upgrade a 1.17 cluster to 1.18 so you say it is normal because the fix was in 1.18 and 1.19 right ?

you may have used the 1.18.0 binary which had the problem. but if you use the kubeadm 1.18.<latest> binary it should work.