First draft of SIG Cluster Lifecycle related relnotes. #391
Conversation
k8s-ci-robot
added
the
cncf-cla: yes
|
@pipejakob: GitHub didn't allow me to assign the following users: wlan0, diegs, mkumatag. Note that only kubernetes members can be assigned. In response to this:
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. |
| * [beta] Support for out-of-tree and out-of-process cloud providers, a.k.a pluggable providers, has been promoted from alpha to beta. ([#88](https://github.com/kubernetes/features/issues/88), [@wlan0](https://github.com/wlan0)) | ||
|
|
||
| #### DaemonSet | ||
| * [beta] DaemonSet upgrades can be achieved via a start-then-kill update strategy. ([#373](https://github.com/kubernetes/features/issues/373), [@aaronlevy](https://github.com/aaronlevy), [@diegs](https://github.com/diegs)) |
release-1.8/release_notes_draft.md
Outdated
|
|
||
| ### **Node Components** | ||
| #### kubelet | ||
| * [alpha] Add limited support for pod "checkpointing" in the kubelet to help enable self-hosting. ([#378](https://github.com/kubernetes/features/issues/378), [@timothysc](https://github.com/timothysc)) |
There was a problem hiding this comment.
@yujuhong I will place a WIP and updated proposal with details by the end of this week.
There was a problem hiding this comment.
Cool. Are the release notes accurate so far? At least for a first draft?
release-1.8/release_notes_draft.md
Outdated
| @@ -44,3 +44,37 @@ please check out the [release notes guidance][] issue. | |||
| ## **Deprecations** | |||
|
|
|||
| ## **Notable Features** | |||
|
|
|||
| ### **Node Components** | |||
| #### kubelet | |||
There was a problem hiding this comment.
Need to add the new alpha CPU manager #375 to this list
[alpha] Support alternative container-level CPU affinity policies using the new kubelet CPU manager. ([#375](https://github.com/kubernetes/features/issues/375), [@sjenning](https://github.com/sjenning), [@ConnorDoyle](https://github.com/ConnorDoyle)
There was a problem hiding this comment.
Also need to add and entry for hugepage support #275
[alpha] Applications may now request pre-allocated hugepages by using the new `hugepages` resource in the container resource requests. [#275](https://github.com/kubernetes/features/issues/275), [@derekwaynecarr](https://github.com/derekwaynecarr)
fyi @derekwaynecarr
There was a problem hiding this comment.
@sjenning this is sig-cluster-lifecycles proposed additions, not sig-node.
There was a problem hiding this comment.
@timothysc oh I see, sorry. Just found out about this hidden process since the release-note tags in feature PRs are apparently not used for anything now.
release-1.8/release_notes_draft.md
Outdated
| * [beta] A new authentication and verification mechanism called Bootstrap Tokens has been added to the core API, which can be used to easily add new members to a cluster. ([#130](https://github.com/kubernetes/features/issues/130), [@luxas](https://github.com/luxas), [@jbeda](https://github.com/jbeda)). | ||
|
|
||
| #### Addons | ||
| * [alpha] A new system addon manager is available that is aiming to improve the downsides of the existing `kube-addons.sh` manager. ([#18](https://github.com/kubernetes/features/issues/18), [@justinsb](https://github.com/justinsb)) |
There was a problem hiding this comment.
ping @justinsb
I don't think this is gonna ship
release-1.8/release_notes_draft.md
Outdated
| * [beta] Kubernetes now has automated continuous-integration tests against all of our supported platforms (amd64, armhfp, aarch64, ppc64le, s390x), to ensure that it continues to work on these platforms. It's also possible to run clusters with nodes of mixed architectures. ([#288](https://github.com/kubernetes/features/issues/288), [@luxas](https://github.com/luxas), [@mkumatag](https://github.com/mkumatag), [@ixdy](https://github.com/ixdy)) | ||
|
|
||
| #### Cloud Providers | ||
| * [beta] Support for out-of-tree and out-of-process cloud providers, a.k.a pluggable providers, has been promoted from alpha to beta. ([#88](https://github.com/kubernetes/features/issues/88), [@wlan0](https://github.com/wlan0)) |
There was a problem hiding this comment.
We haven't decided as a group whether this should become beta or stay in alpha yet
release-1.8/release_notes_draft.md
Outdated
|
|
||
| #### Cluster Discovery/Bootstrap | ||
|
|
||
| * [beta] A new authentication and verification mechanism called Bootstrap Tokens has been added to the core API, which can be used to easily add new members to a cluster. ([#130](https://github.com/kubernetes/features/issues/130), [@luxas](https://github.com/luxas), [@jbeda](https://github.com/jbeda)). |
There was a problem hiding this comment.
maybe drop new? (It has been there since v1.6)
release-1.8/release_notes_draft.md
Outdated
| #### kubeadm | ||
| * [beta] A new `phase` subcommand supports performing only subtasks of the full `kubeadm init` flow. Combined with fine-grained configuration, kubeadm is now more easily consumable by higher-level provisioning tools like kops or GKE. ([#356](https://github.com/kubernetes/features/issues/356), [@luxas](https://github.com/luxas), [@justinsb](https://github.com/justinsb)) | ||
|
|
||
| * [alpha] A new `upgrade` subcommand allows you to automatically upgrade a self-hosted cluster created with kubeadm. ([#296](https://github.com/kubernetes/features/issues/296), [@luxas](https://github.com/luxas)) |
There was a problem hiding this comment.
Should be [beta]. Not sure whether self-hosted will be true or not, but I'm fine with leaving that as-is, as I think we're gonna meet the deadline for self-hosting upgrades as well (add-first-then-kill)
|
I've updated a few things based on feedback in a new commit so it's easy to see what changed. I'll squash into one commit before merging (after an LGTM). |
release-1.8/release_notes_draft.md
Outdated
| * [alpha] A new system addon manager is available that is aiming to improve the downsides of the existing `kube-addons.sh` manager. ([#18](https://github.com/kubernetes/features/issues/18), [@justinsb](https://github.com/justinsb)) | ||
|
|
||
| #### Multi-platform | ||
| * [beta] Kubernetes now has automated continuous-integration tests against all of our supported platforms (amd64, armhfp, aarch64, ppc64le, s390x), to ensure that it continues to work on these platforms. It's also possible to run clusters with nodes of mixed architectures. ([#288](https://github.com/kubernetes/features/issues/288), [@luxas](https://github.com/luxas), [@mkumatag](https://github.com/mkumatag), [@ixdy](https://github.com/ixdy)) |
There was a problem hiding this comment.
Not really sure whether we can say we have automated CI tests. All we have is conformance tests running on platforms ( amd64, armhfp, aarch64, ppc64le). @luxas WDYT?
Note - remove s390x from the list because we don't have all the required images.
There was a problem hiding this comment.
I'll strip out s390x. Will we have automated CI tests by the 1.8 release, or is the new goal just to have conformance tests running manually for these architectures by then?
There was a problem hiding this comment.
Just let me know if I should rip out the entry altogether, or modify it to say something else. I would also recommend updating the feature issue #288 if the scope or timeline has changed.
pipejakob
force-pushed
the
1.8-lifecycle
branch
from
6c53490
to
1a3ca17
Compare
Our draft was already merged, so checking off the SIG from the checklist. kubernetes#391
Our release notes draft was already merged, so checking the SIG off from the checklist. kubernetes#391
These are mostly populated from the issues labeled for sig/cluster-lifecycle and 1.8. I have reworded them in places to change from future to past tense and have more consistent verbiage.
CC @timothysc @luxas @justinsb @jbeda @mkumatag @ixdy @wlan0 @aaronlevy @diegs
Could everyone on the above CC list please take a look at the feature(s) you own and sign off on their representation here?
Also, if there is anything that is definitely going to slip the 1.8 release, now is a good time to pull it out of the release notes and update its issue.