Change:
ProcMountType:                                  {Default: false, PreRelease: featuregate.Alpha}, TTLAfterFinished:                               {Default: false, PreRelease: featuregate.Alpha}, KubeletPodResources:                            {Default: true, PreRelease: featuregate.Beta}, <del> WindowsGMSA:                                    {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.20 WindowsRunAsUserName:                           {Default: true, PreRelease: featuregate.GA, LockToDefault: true}, // remove in 1.20 </del> LocalStorageCapacityIsolationFSQuotaMonitoring: {Default: false, PreRelease: featuregate.Alpha}, NonPreemptingPriority:                          {Default: true, PreRelease: featuregate.Beta}, PodOverhead:                                    {Default: true, PreRelease: featuregate.Beta},

Discussion:
Both WindowsGMSA and WindowsRunAsUserName feature gates have been GA since v1.18 and were scheduled to be removed in v1.20. /sig windows /milestone v1.20 /good-first-issue
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 : Both WindowsGMSA and WindowsRunAsUserName feature gates have been GA since v1.18 and were scheduled to be removed in v1.20. /milestone v1.20 /good-first-issue 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
/triage accepted
Hi, how can i help with that?
Delete the codes related to these two feature gates, because they have been GA and are enabled by default
Yup, feel free to assign the issue to yourselft and then remove the features gates from the file listed above and any other places they are used in code. Thanks!
Hey, can i take this up ?
/assign
It seems that proposed it first. You can communicate with him before you start.
ok sure
/assign
Hi, Sorry by delay, but i cant push the issue branch and receive: fatal: unable to access '': The requested URL returned error: 403 I already fill the form to contriburter. Any sugestion? Regards
Before you start, you can read
i already assing to CLA and make a new branch issue-. But when i push the branch my permission is denny. any tips? Tkz
Try forking the kubernetes/kubernetes repository and then creating the pull request from a branch in your personal github repository.
Tkz, I create a PR, but i received: cla/linuxfoundation — commit missing GitHub user but i already do it. Whats is wrong?
Ok, i found the error. My name in git was wrong. Sorry, Im waiting the result for PR. Tkz
Now, i waiting for
Hi everyone, Is normal waiting this itens, or I must provide then? Tkz
Ok, Em ter., 20 de out.

de 2020 às 15:47, Mark Rossetti < : Doutor em Ciência da Computação na UNICAMP
When your code is ready, you can pull a pr from your own repo to kubernetes' repo~~ Remember to read the connection I posted earlier and the sub-connections inside.
Hi , we already past the code freeze for v1.20 and the release is due next week. At this point in time, we are considering only changes which are release blocking. Hence, I am removing this from the v1.20 milestone. Please feel to ping us on if you feel otherwise. /milestone clear
Hey Is there anything that can be done here?
Hi ! can I take this? anything required?
Hi, yes of course. Nothing to relate. Em ter., 19 de jan. de 2021 às 13:24, coderfornow <: Doutor em Ciência da Computação na UNICAMP
/assign