-
Notifications
You must be signed in to change notification settings - Fork 39.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Graduate the kubeletconfig API to beta #53084
Comments
…-kubeletconfig Automatic merge from submit-queue (batch tested with PRs 53204, 53364, 53559, 53589, 53088). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Mulligan: Remove deprecated and experimental fields from KubeletConfiguration Revert "Merge pull request #51857 from kubernetes/revert-51307-kc-type-refactor" This reverts commit 9d27d92, reversing changes made to 2e69d4e. See original: #51307 We punted this from 1.8 so it could go through an API review. The point of this PR is that we are trying to stabilize the kubeletconfig API so that we can move it out of alpha, and unblock features like Dynamic Kubelet Config, Kubelet loading its initial config from a file instead of flags, kubeadm and other install tools having a versioned API to rely on, etc. We shouldn't rev the version without both removing all the deprecated junk from the KubeletConfiguration struct, and without (at least temporarily) removing all of the fields that have "Experimental" in their names. It wouldn't make sense to lock in to deprecated fields. "Experimental" fields can be audited on a 1-by-1 basis after this PR, and if found to be stable (or sufficiently alpha-gated), can be restored to the KubeletConfiguration without the "Experimental" prefix. Related issue: #53084 **Release note**: ```release-note NONE ``` /cc @kubernetes/api-reviewers
@mtaufen what else is needed for 1.9? (or can we move this to 1.10)? |
There's a checklist in this PR: #53833 |
We're very close |
[MILESTONENOTIFIER] Milestone Removed From Issue @mtaufen @kubernetes/sig-cluster-lifecycle-misc @kubernetes/sig-node-misc Important: Code freeze is in effect and only issues with |
@mtaufen repurposed for v1.10 |
Thanks @luxas
…On Fri, Dec 22, 2017 at 4:36 AM, Lucas Käldström ***@***.***> wrote:
@mtaufen <https://github.com/mtaufen> repurposed for v1.10
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#53084 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA3JwXsddIvxL-PYMNr1C9bmcq4ycitEks5tC6JMgaJpZM4Pk-JU>
.
--
Michael Taufen
Google SWE
|
is this on track for 1.10? I don't show any activity in this issue since December. |
This can be closed, it's done. |
@kubernetes/sig-cluster-lifecycle-misc (we should move to enable asap). |
@mtaufen @timothysc does it mean that we should enable |
No, this is for the kubelet's config file API (and, equivalently, the serialized payload you send in a ConfigMap when using dynamic config). The surrounding machinery that delivers the payload for dynamic config is still considered alpha. |
Goal is to hit beta in 1.10, wrt kubernetes/enhancements#281
The text was updated successfully, but these errors were encountered: