fix: The contrasting statements and descriptions are inconsistent for kube version

[my-git9]

The fail msg in https://github.com/kubernetes-sigs/kubespray/compare/master...my-git9:kubeversion?expand=1#diff-4da0e67b40b4f087f4528beccf9e990aa66cf96682581fce12a9801ff464b204L4:

msg: "Kubeadm version {{ kubeadm_version }} do not matches kubernetes {{ kube_version }}"

What should be compared here is the kube and kubeadm versions

What type of PR is this?

/kind bug

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[yankay]

Thanks @my-git9

Because the code is from PR #6302.
@caruccio @floryut , would you please help to review it :-)

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: my-git9, yankay

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:

• OWNERS [yankay]

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

[VannTen]

Actually, this check does not really make sense:
We allow to customize kubeadm_version (it's defined in roles/kubespray-defaults/main/download.yml).

If we don't want to do that (which seems the intention of that check) we should just not allow the modification of kubeadm_version, by movings into vars/ instead, and get rid of the check.