Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

Welcome @cyclinder!

It looks like this is your first PR to kubernetes/kubernetes 🎉. 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/kubernetes 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. 😃

Hi @cyclinder. Thanks for your PR.

I'm waiting for a kubernetes 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.

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

/retest

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

/ok-to-test
/check-cla

/check-cla

/assign @mtaufen

@ehashman would you have time to take a look again？

Who is the current owner of the feature? They should review this.

@wojtek-t is it you?

/assign @wojtek-t

/lgtm
/approve

/assign @liggitt - for API approval

/approve
for API field doc change

/hold in case @wojtek-t wanted #105222 (comment) addressed before merge

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cyclinder, liggitt, wojtek-t

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

The pull request process is described here

/lgtm

/hold cancel

Shouldn't this have a small release note, to confirm that the kubelet no longer recognizes this feature gate?

Shouldn't this have a small release note, to confirm that the kubelet no longer recognizes this feature gate?

Good point - added.