Change:
When should it be removed? /sig network /kind cleanup
/triage unresolved Comment when the issue is assessed and confirmed. I am a bot run by vllry. ‍
/assign
Feature is GA since 1.11 - Any reference to this Feature Gate needs to be removed from the code, README and Docs: If you're a new contributor, please step in, take this issue, make the PRs, assign it to me with /assign and I'll be glad to help you through the journey of contributing :) /good-first-issue /help
This request has been marked as suitable for new contributors. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : Feature is GA since 1.11 - /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/assign
are you willing to take this one?
Yes. I'm a new contributor.I will to try to complete it.
/assign Welcome! Let me know if you need any kind of help. Please take a look also into the Kubernetes Contributors documentation - When you're ready to create your first PR, please assign it to me and I'll make the first pass!
/sig docs We don't remove GA feature gates from the website; we move them to

Discussion:
// Postpone deletion of a PV or a PVC when they are being used StorageObjectInUseProtection featuregate.Feature = "StorageObjectInUseProtection" <del> // owner: @m1093782566 // GA: v1.11 // // Implement IPVS-based in-cluster service load balancing SupportIPVSProxyMode featuregate.Feature = "SupportIPVSProxyMode" </del> // owner: @dims, @derekwaynecarr // alpha: v1.10 // beta: v1.14

CSINodeInfo:                    {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.19 BlockVolume:                    {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.20 StorageObjectInUseProtection:   {Default: true, PreRelease: featuregate.GA}, <del> SupportIPVSProxyMode:           {Default: true, PreRelease: featuregate.GA}, </del> SupportPodPidsLimit:            {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.21 SupportNodePidsLimit:           {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.21 HyperVContainer:                {Default: false, PreRelease: featuregate.Alpha},

### Cluster Created by Kubeadm <del> If you are using kubeadm with a [configuration file](https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/#config-file), you have to add `mode: ipvs` and also add `SupportIPVSProxyMode: true` below the `kubeProxy` field as part of the kubeadm configuration. </del> <ins> If you are using kubeadm with a [configuration file](https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/#config-file), you have to add `mode: ipvs` below the `kubeProxy` field as part of the kubeadm configuration. </ins> ```yaml ... kubeProxy: config: <del> featureGates: SupportIPVSProxyMode: true </del> mode: ipvs ... ``` <del> Note that in Kubernetes 1.11 and later, `SupportIPVSProxyMode` is set to `true` by default. </del> before running `kube init --config <path_to_configuration_file>` <del> If you are using Kubernetes v1.8, you can also add the flag `--feature-gates=SupportIPVSProxyMode=true` (deprecated since v1.9) in `kubeadm init` command ``` kubeadm init --feature-gates=SupportIPVSProxyMode=true ``` </del> to specify the ipvs mode before deploying the cluster. **Notes**

Use the following check list to help you solve the problems: <del> **1. Enable IPVS feature gateway** For Kubernetes v1.10 and later, feature gate `SupportIPVSProxyMode` is set to `true` by default. However, you need to enable `--feature-gates=SupportIPVSProxyMode=true` explicitly for Kubernetes before v1.10. **2. Specify proxy-mode=ipvs** </del> <ins> **1. Specify proxy-mode=ipvs** </ins> Check whether the kube-proxy mode has been set to `ipvs`. <del> **3. Install required kernel modules and packages** </del> <ins> **2. Install required kernel modules and packages** </ins> Check whether the IPVS required kernel modules have been compiled into the kernel and packages installed. (see Prerequisite)