Remove unnecessary condition check when updating server field in kube-proxy kubeconfig

[lazybetrayer]

What type of PR is this?

/kind bug

What this PR does / why we need it:

When updating cluster, these tasks are skipped since kubernetes/kubeadm is only executed for non-master nodes, and the server field in kube-proxy cm is not correctly changed.

Also these tasks are delegated to the first master and run only once, I think there's no need to add this check.

Which issue(s) this PR fixes:

Fixes #6731

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Hi @lazybetrayer. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[LuckySB]

/ok-to-test
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lazybetrayer, LuckySB

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 [LuckySB]

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

[LuckySB]

nice catch
/lgtm