Code change:
On: But I get: Sorry, I can't provide a PR at this moment.
/kind bug /sig node /language en /priority important-longterm Static pods are on the syllabus for the CKA qualification, so we should especially avoid recommending a deprecated approach.
Maybe it makes sense to change to docs from to , too, since that what kubeadm creates.
This has been previously discussed within the SIG; migrating off of command line flags is a backlog item. Other components have a similar problem. For the foreseeable future, the command line flags will definitely work and continue to be supported. We are ensuring any new command line flags are as config options and attempting to migrate over any flags that are not currently supported in the config API. So, while technically deprecated, I think this is still okay. It would be great to have docs for both.
/triage accepted
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
I think this is still worth tracking, but isn't a short term priority. /reopen /lifecycle frozen
Reopened this issue. <detailsIn response to : I think this is still worth tracking, but isn't a short term priority. /lifecycle frozen 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
/help
This request has been marked as needing help from a contributor. 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 : /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
/retitle Create static Pods: has been deprecated
/assign I will try to work on a PR for this issue.

Related discussion:
text: EOF ``` <del> 1. Configure your kubelet on the node to use this directory by running it with </del> <ins> 1. Configure the kubelet on that node to set a `staticPodPath` value in the [kubelet configuration file](/docs/reference/config-api/kubelet-config.v1beta1/). See [Set Kubelet Parameters Via A Configuration File](/docs/tasks/administer-cluster/kubelet-config-file/) for more information. An alternative and deprecated method is to configure the kubelet on that node to look for static Pod manifests locally, using a command line argument. To use the deprecated approach, start the kubelet with the </ins> `--pod-manifest-path=/etc/kubernetes/manifests/` argument. <del> On Fedora, edit `/etc/kubernetes/kubelet` to include this line: ``` KUBELET_ARGS="--cluster-dns=10.254.0.10 --cluster-domain=kube.local --pod-manifest-path=/etc/kubernetes/manifests/" ``` or add the `staticPodPath: <the directory>` field in the [kubelet configuration file](/docs/reference/config-api/kubelet-config.v1beta1/). </del> 1. Restart the kubelet. On Fedora, you would run: ```shell