Migrate Kubelet --dynamic-config-dir to kubelet.config.k8s.io or remove the flag

[mtaufen]

Flag name: dynamic-config-dir

Help text:

The Kubelet will use this directory for checkpointing downloaded configurations and tracking configuration health. The Kubelet will create this directory if it does not already exist. The path may be absolute or relative; relative paths start at the Kubelet's current working directory. Providing this flag enables dynamic Kubelet configuration. Presently, you must also enable the DynamicKubeletConfig feature gate to pass this flag.

---

This is part of migrating the Kubelet command-line to a Kubernetes-style API.

The --dynamic-config-dir flag should either be migrated to the Kubelet's kubelet.config.k8s.io
API group, or simply removed from the Kubelet.

If this could be considered an instance-specific flag, or a descriptor of local topology
managed by the Kubelet, see: #61647.

If this flag is only registered in os-specific builds, see: #61649.

@sig-node-pr-reviews @sig-node-api-reviews

/assign @mtaufen
/sig node
/kind feature
/priority important-soon
/milestone v1.11
/status approved-for-milestone

[mtaufen]

Local, kubelet-managed topology.

[tianshapjq]

should this be coherent with --root-dir?

[k8s-github-robot]

[MILESTONENOTIFIER] Milestone Issue Needs Attention

@mtaufen @kubernetes/sig-node-misc

Action required: During code slush, issues in the milestone should be in progress.
If this issue is not being actively worked on, please remove it from the milestone.
If it is being worked on, please add the status/in-progress label so it can be tracked with other in-flight issues.

Note: If this issue is not resolved or labeled as priority/critical-urgent by Tuesday, June 5th it will be moved out of the v1.11 milestone.

Issue Labels

• sig/node: Issue will be escalated to these SIGs if needed.
• priority/important-soon: Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts.
• kind/feature: New functionality.

Help

• Additional instructions
• Commands for setting labels

[mtaufen]

/milestone clear

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[mtaufen]

/remove-lifecycle rotten /lifecycle frozen

…

On Mon, Oct 22, 2018 at 8:27 AM fejta-bot ***@***.***> wrote: Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Send feedback to sig-testing, kubernetes/test-infra and/or fejta <https://github.com/fejta>. /lifecycle rotten — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#61673 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA3Jwb03x9SSrZnQQNjds-uwzEWXekREks5unePggaJpZM4S6V63> .

-- Michael Taufen Google SWE

[SergeyKanzhelev]

Since the feature is scheduled for deprecation, closing the issue.

KEP: kubernetes/enhancements#281

/close

[k8s-ci-robot]

@SergeyKanzhelev: Closing this issue.

In response to this:

Since the feature is scheduled for deprecation, closing the issue.

KEP: kubernetes/enhancements#281

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.