Change:
[Network Plugins](/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/) allow Kubernetes to work with different networking topologies and technologies. <ins> ### Kubelet image credential provider plugins {{< feature-state for_k8s_version="v1.26" state="stable" >}} Kubelet image credential providers are plugins for the kubelet to dynamically retrieve image registry credentials. The credentials are then used when pulling images from container image registries that match the configuration. The plugins can communicate with external services or use local files to obtain credentials. This way, the kubelet does not need to have static credentials for each registry, and can support various authentication methods and protocols. For plugin configuration details, see [Configure a kubelet image credential provider](/docs/tasks/administer-cluster/kubelet-credential-provider/). </ins> ## Scheduling extensions The scheduler is a special type of controller that watches pods, and assigns

Discussion:
This is a Feature 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 Mention kubelet image credential providers within Why is this needed The concepts section about does not list kubelet credential providers. exists but largely in isolation; you'd have to know it existed to find it. It's also OK to mention this concept elsewhere - and especially encouraged if the feature looks likely to graduate towards beta. Comments /sig node /language en /kind feature
/triage accepted /sig docs
I would like to work on this
/assign
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Mark this issue or PR as rotten with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at . /lifecycle stale [1]:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules: After 90d of inactivity, is applied After 30d of inactivity since was applied, is applied After 30d of inactivity since was applied, the issue is closed You can: Mark this issue or PR as fresh with Close this issue or PR with Offer to help out with [Issue Triage][1] Please send feedback to sig-contributor-experience at .

/lifecycle rotten [1]:
/remove-lifecycle rotten
/priority backlog
I don't see any updates from so unassigning Feel free to assign it if you are interested in taking it up. Thanks! /unassign
The removals of in-tree support - eg - make this documentation more important.
/assign