Remove extra parameter kube_proxy_remove

[EDGsheryl]

Signed-off-by: EDGsheryl edgsheryl@gmail.com

What type of PR is this?

/kind bug
/kind cleanup
/kind documentation

What this PR does / why we need it:

I noticed that the runbook failed when I enable the calico_bpf_enabled, so I trace the issue, I found that #6512 had removed the kube_proxy_remove, but it still exist in the runbook, so I clean it up.

Which issue(s) this PR fixes:

Fixes #8149

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[k8s-ci-robot]

Welcome @EDGsheryl!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @EDGsheryl. 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.

[cristicalin]

@EDGshery please rebase on latest master branch to make the CI happy (see #8157)

[EDGsheryl]

/retest

[k8s-ci-robot]

@EDGsheryl: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[EDGsheryl]

@EDGshery please rebase on latest master branch to make the CI happy (see #8157)

Sure, thanks.

[cristicalin]

Thanks for the fix @EDGsheryl !

/ok-to-test
/lgtm

[floryut]

👍

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: EDGsheryl, floryut

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

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