Change:
## API removals, deprecations, and other changes for Kubernetes 1.24 <del> * [Dynamic kubelet configuration](https://github.com/kubernetes/enhancements/issues/281): `DynamicKubeletConfig` is used to enable the dynamic configuration of the kubelet. The `DynamicKubeletConfig` flag was deprecated in Kubernetes 1.22. In v1.24, this feature gate will be removed from the kubelet. See [Reconfigure kubelet](/docs/tasks/administer-cluster/reconfigure-kubelet/). Refer to the ["Dynamic kubelet config is removed" KEP](https://github.com/kubernetes/enhancements/issues/281) for more information. </del> <ins> * [Dynamic kubelet configuration](https://github.com/kubernetes/enhancements/issues/281): `DynamicKubeletConfig` is used to enable the dynamic configuration of the kubelet. The `DynamicKubeletConfig` flag was deprecated in Kubernetes 1.22. In v1.24, this feature gate will be removed from the kubelet. Refer to the ["Dynamic kubelet config is removed" KEP](https://github.com/kubernetes/enhancements/issues/281) for more information. </ins> * [Dynamic log sanitization](https://github.com/kubernetes/kubernetes/pull/107207): The experimental dynamic log sanitization feature is deprecated and will be removed in v1.24. This feature introduced a logging filter that could be applied to all Kubernetes system components logs to prevent various types of sensitive information from leaking via logs. Refer to [KEP-1753: Kubernetes system components logs sanitization](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/1753-logs-sanitization#deprecation) for more information and an [alternative approach](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/1753-logs-sanitization#alternatives=). * [Removing Dockershim from kubelet](https://github.com/kubernetes/enhancements/issues/2221): the Container Runtime Interface (CRI) for Docker (i.e. Dockershim) is currently a built-in container runtime in the kubelet code base. It was deprecated in v1.20. As of v1.24, the kubelet will no longer have dockershim. Check out this blog on [what you need to do be ready for v1.24](/blog/2022/03/31/ready-for-dockershim-removal/). * [Storage capacity tracking for pod scheduling](https://github.com/kubernetes/enhancements/issues/1472): The CSIStorageCapacity API supports exposing currently available storage capacity via CSIStorageCapacity objects and enhances scheduling of pods that use CSI volumes with late binding. In v1.24, the CSIStorageCapacity API will be stable. The API graduating to stable initates the deprecation of the v1beta1 CSIStorageCapacity API. Refer to the [Storage Capacity Constraints for Pod Scheduling KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1472-storage-capacity-tracking) for more information.

Discussion:
This is a Cleanup Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be removed Remove Why is this needed v1.24 of Kubernetes will remove the dynamic kubelet config feature (deprecated since Kubernetes v1.22) Comments /sig node /language en /milestone 1.24
/triage accepted
See
/assign
~BTW Any PR for this should target the branch dev-1.24~ That advice is now stale. Kubernetes v1.24 has shipped.
Okay... But I want to clear that you want me to remove the entire page from "Administer a Cluster" . Am I Right ?
/assign
This won't be in 1.24's docs, clearing the milestone. This can be to subsequent milestones if needed. (or closed if I'm missing a PR somewhere) /milestone clear
We should have updated the page to state when the removal is due, or to remove the commitment if we're no longer sure.
/label good-first-issue All you need to do is remove from the docs.
The label(s) /label good-first-issue api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactorlabels -additionallabelslabels -? <detailsIn response to : /label 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
/good-first-issue states that the feature was removed. why did we take this change out of the v1.24 milestone?
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command.

<detailsIn response to : /good-first-issue states that the feature was removed. 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
should I also remove all the links that lead to ? for example, here:
/remove-milestone 1.24
Not required, but much better if you do.
hey, I have made the required changes in the PR, could you please review it?
can i work on this issue as well?
You're welcome to. The next step on contributing is to review
will do !
hey , this is my contribution and i would be glad to help and have an insight. can you tell me what to do? im new, just trying to get familiar with all of this
How to work on this: Please open a PR that removes If there are any other English pages that link to then please turn the links into plain text, or otherwise fix them up.
/assign
The issue has been resolved. all are removed or commented out. still there are some mention of this like but they there only to point out that the dynamic kubelet config is removed from v1.24.
I don't see any updates from your side; so unassigning you. Please feel free to assign, if you come back here again and are willing to work on /unassign
i think this issue is resolved.
If is addressed somewhere in the PR then can you please share a link of the respective PR? Thanks!
Can I work on this issue is this still open ?
heyyo can you please confirm what branch this issue fix needs to be targeted on? Thanks in advance:)
To remove that page, make the change to the main branch. Ideally, also find any English pages - just English - that link to and edit them so that they don't.
/assign
Hi This is my first contribution to open source, I have deleted the requested page. Should I proceed to open a pull request?
heyyo if you don't mind I was already working on the issue and have made the changes three days ago just haven't pushed them yet
of course! I noticed you did not claim the issue with the bot so I thought I was good to go :)
/assign
update : will create a PR tomorrow.

/assign
is this issue still open ??
Hi, I want to work on this. Is this stll open ?
/assign
Hi. There's a white-on-green “Open” marker at the left of the top navigation, at least in the default desktop view. That indicates that the issue is open. Anyone is welcome to suggest a fix, or to propose closing the issue if the fix has already happened. I can see that the page is still there at the time of writing.
hi I can fix this issue u can assign me it.
/assign
where are the html file of this page in the repo