Initial version of release notes markdown #92

nickchase · 2018-03-24T01:52:44Z

No description provided.

dims · 2018-03-24T01:58:44Z

calebamiles · 2018-03-24T06:52:13Z

releases/release-1.10/release-notes-draft.md


-This will will be used to track release notes for Kubernetes 1.10.
+[[TOC]]


please drop as will be added automatically

calebamiles

Also missing information on external dependencies

I do really like the extra attention paid to the copy in the Major Themes section though 👍 🥇

calebamiles · 2018-03-24T06:53:21Z

releases/release-1.10/release-notes-draft.md

+
+### Sig-node
+
+Control also figures into changes within SIG-Node, with the beta release of [Dynamic Kubelet Configuration](https://github.com/kubernetes/features/issues/281), the ability to make changes to Kubelet without having to bring down the node, and alpha support for the ability to [configure whether containers in a pod should share a single process namespace](https://github.com/kubernetes/features/issues/495), The CRI has also seen some improvements, with support for  [support for Windows Container Configuration](https://github.com/kubernetes/features/issues/547) and the beta release of the [CRI validation test suite](https://github.com/kubernetes/features/issues/292). In addition, this release includes alpha support for [Debug Containers](https://github.com/kubernetes/features/issues/277).


Control also figures into changes within SIG-Node

maybe this block had been placed after some text which mentioned "control"? Possibly reword the intro

Fixed, thanks!

calebamiles · 2018-03-24T06:54:25Z

releases/release-1.10/release-notes-draft.md

+
+Control also figures into changes within SIG-Node, with the beta release of [Dynamic Kubelet Configuration](https://github.com/kubernetes/features/issues/281), the ability to make changes to Kubelet without having to bring down the node, and alpha support for the ability to [configure whether containers in a pod should share a single process namespace](https://github.com/kubernetes/features/issues/495), The CRI has also seen some improvements, with support for  [support for Windows Container Configuration](https://github.com/kubernetes/features/issues/547) and the beta release of the [CRI validation test suite](https://github.com/kubernetes/features/issues/292). In addition, this release includes alpha support for [Debug Containers](https://github.com/kubernetes/features/issues/277).
+
+The Resource Management Working Group graduated three features to Beta in the 1.10 release.  First, [CPU Manager](https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/), which allows users to request exclusive CPU cores.  This helps performance in a variety of use-cases, including network latency sensitive applications, as well as applications that benefit from CPU cache residency.  Next, [Huge Pages](https://kubernetes.io/docs/tasks/manage-hugepages/scheduling-hugepages/), which allows pods to consume either 2Mi or 1Gi Huge Pages.  This benefits applications that consume large amounts of memory.  Use of Huge Pages is a common tuning recommendation for databases and JVMs.  Finally, the [Device Plugin](https://kubernetes.io/docs/concepts/cluster-administration/device-plugins/) feature, which provides a framework for vendors to advertise their resources to the Kubelet without changing Kubernetes core code.  Targeted devices include GPUs, High-performance NICs, FPGAs, InfiniBand, and other similar computing resources that may require vendor specific initialization and setup.


Beta vs "stable" vs stable used elsewhere

changed to beta

calebamiles · 2018-03-24T06:58:53Z

releases/release-1.10/release-notes-draft.md

+
+* Volume metrics support for vSphere Cloud Provider has been added. You can now monitor available space, capacity, and used space on volumes created using vSphere. ([#59328](https://github.com/kubernetes/kubernetes/pull/59328), [@divyenpatel]([https://github.com/divyenpatel](https://github.com/divyenpatel)))
+
+* Emit number of bound and unbound persistent volumes as Metrics. This PR adds four kinds of Volume Metrics for kube-controller-manager: bound PVC numbers, unbound PVC numbers, bound PV numbers and unbound PV numbers. The PVC metrics use namespace as dimension and the PV metrics use Sto


Sig-API-Machinery vs Sig-api-machinery. Also maybe drop "Sig" altogether

Agree with Caleb on this. Also, it would be SIG, not Sig anyway.

Removed "Sig" nomenclature

liggitt · 2018-03-24T20:31:58Z

releases/release-1.10/release-notes-draft.md

+
+([#57613](https://github.com/kubernetes/kubernetes/pull/57613), [@mtaufen]([https://github.com/mtaufen](https://github.com/mtaufen)))
+
+* The boostrapped RBAC role and rolebinding for the `cloud-provider` service account is now deprecated. If you're currently using this service account, you must create and apply your own [RBAC polic](https://kubernetes.io/docs/admin/authorization/rbac/)[y](https://kubernetes.io/docs/admin/authorization/rbac/) for new clusters. ([#59949](https://github.com/kubernetes/kubernetes/pull/59949), [@nicksardo]([https://github.com/nicksardo](https://github.com/nicksardo)))


weird link split "polic" and "y" are linked separately

liggitt · 2018-03-24T20:34:59Z

releases/release-1.10/release-notes-draft.md

+This section is still in flux.  Please make sure all issues are documented in the known Issue accumulator: [https://github.com/kubernetes/kubernetes/issues/59764](https://github.com/kubernetes/kubernetes/issues/59764)
+
+# Deprecations
+


the etcd2 deprecation (first announced in 1.9) is significant enough that I think we should repeat it in every release until support is removed.

Suggest adding:

etcd2 as a backend is deprecated and support will be removed in Kubernetes 1.13

cc @kubernetes/sig-api-machinery-pr-reviews

jdumars · 2018-03-25T00:29:31Z

releases/release-1.10/release-notes-draft.md

+
+* Volume metrics support for vSphere Cloud Provider has been added. You can now monitor available space, capacity, and used space on volumes created using vSphere. ([#59328](https://github.com/kubernetes/kubernetes/pull/59328), [@divyenpatel]([https://github.com/divyenpatel](https://github.com/divyenpatel)))
+
+* Emit number of bound and unbound persistent volumes as Metrics. This PR adds four kinds of Volume Metrics for kube-controller-manager: bound PVC numbers, unbound PVC numbers, bound PV numbers and unbound PV numbers. The PVC metrics use namespace as dimension and the PV metrics use Sto


This has not merged.

jdumars · 2018-03-25T00:31:02Z

releases/release-1.10/release-notes-draft.md

+
+* Volume metrics support for vSphere Cloud Provider has been added. You can now monitor available space, capacity, and used space on volumes created using vSphere. ([#59328](https://github.com/kubernetes/kubernetes/pull/59328), [@divyenpatel]([https://github.com/divyenpatel](https://github.com/divyenpatel)))
+
+* Emit number of bound and unbound persistent volumes as Metrics. This PR adds four kinds of Volume Metrics for kube-controller-manager: bound PVC numbers, unbound PVC numbers, bound PV numbers and unbound PV numbers. The PVC metrics use namespace as dimension and the PV metrics use Sto


Not going in.

jdumars · 2018-03-25T00:32:23Z

releases/release-1.10/release-notes-draft.md

+
+* Volume metrics support for vSphere Cloud Provider has been added. You can now monitor available space, capacity, and used space on volumes created using vSphere. ([#59328](https://github.com/kubernetes/kubernetes/pull/59328), [@divyenpatel]([https://github.com/divyenpatel](https://github.com/divyenpatel)))
+
+* Emit number of bound and unbound persistent volumes as Metrics. This PR adds four kinds of Volume Metrics for kube-controller-manager: bound PVC numbers, unbound PVC numbers, bound PV numbers and unbound PV numbers. The PVC metrics use namespace as dimension and the PV metrics use Sto


Does not need a release note. It's behind and alpha feature gate, per @msau42

nikhita · 2018-03-25T12:04:36Z

releases/release-1.10/release-notes-draft.md

+
+* In-place node upgrades to this release from versions 1.7.14, 1.8.9, and 1.9.4 are not supported if using subpath volumes with PVCs.  Such pods should be drained from the node first.
+
+* The Container Runtime Interface (CRI) version has increased from v1alpha1 to v1alpha2. Runtimes implementing the CRI will need to update to the new version, which configures container namespaces using an enumeration rather than booleans. This change to the alpha API is not backwards compatible; implementations of the CRI such as containerd, will need to update to the new API version. ([#58973](https://github.com/kubernetes/kubernetes/pull/58973), [@verb]([https://github.com/verb](https://github.com/verb)))


nit: usernames are not linked correctly.
should be [@verb](https://github.com/verb).

also applicable at many places below.

Conversion artifact; fixed.

nikhita · 2018-03-25T12:05:18Z

releases/release-1.10/release-notes-draft.md

+
+KubeProxyConfiguration Before:
+
+apiVersion: kubeproxy.config.k8s.io/v1alpha1


needs formatting

nikhita · 2018-03-25T12:11:07Z

releases/release-1.10/release-notes-draft.md

+
+* Volume metrics support for vSphere Cloud Provider has been added. You can now monitor available space, capacity, and used space on volumes created using vSphere. ([#59328](https://github.com/kubernetes/kubernetes/pull/59328), [@divyenpatel]([https://github.com/divyenpatel](https://github.com/divyenpatel)))
+
+* Emit number of bound and unbound persistent volumes as Metrics. This PR adds four kinds of Volume Metrics for kube-controller-manager: bound PVC numbers, unbound PVC numbers, bound PV numbers and unbound PV numbers. The PVC metrics use namespace as dimension and the PV metrics use Sto


Can we link to the docs here? The linked PR is the implementation PR and contains implementation details (which users don't need to care about).

Docs link, which will work when 1.10 is released: https://kubernetes.io/docs/tasks/access-kubernetes-api/extend-api-custom-resource-definitions/#subresources

Err, I'm not sure why Github is showing this comment for line 541. I meant this for the subresources release note: https://github.com/kubernetes/sig-release/pull/92/files#diff-fbb7988712c575e744f5f9d12b9f4392R617

dixudx · 2018-03-26T02:33:01Z

releases/release-1.10/release-notes-draft.md

+
+* `kubectl scale` can now scale any resource (kube, CRD, aggregate) conforming to the standard scale endpoint ([#58298](https://github.com/kubernetes/kubernetes/pull/58298), [@p0lyn0mial](https://github.com/p0lyn0mial))
+
+* Cluster Autoscaler has been updated to Version 1.2.0, which includes fixes around GPUs and base image change. See [https://github.com/kubernetes/autoscaler/releases/tag/cluster-autoscaler-](https://github.com/kubernetes/autoscaler/rel


Dup with L911?

Yes. Line 911.

Of course (doh). Got it.

feiskyer · 2018-03-26T03:18:34Z

releases/release-1.10/release-notes-draft.md

+
+### Node
+
+Many of the changes within SIG-Node revolve around control, with the beta release of [Dynamic Kubelet Configuration](https://github.com/kubernetes/features/issues/281), the ability to make changes to Kubelet without having to bring down the node, and alpha support for the ability to [configure whether containers in a pod should share a single process namespace](https://github.com/kubernetes/features/issues/495), The CRI has also seen some improvements, with support for  [support for Windows Container Configuration](https://github.com/kubernetes/features/issues/547) and the beta release of the [CRI validation test suite](https://github.com/kubernetes/features/issues/292). In addition, this release includes alpha support for [Debug Containers](https://github.com/kubernetes/features/issues/277).


s/The CRI has also seen some improvements/The CRI has also beem upgrade to v1alpha2/

Also Debug Containers feature has been moved outside of v1.10

Moved 61411/61412 (DaemonSets) to Known Issues.

* Use of subPath module with hostPath volumes can cause issues during reconstruction ([#61446](kubernetes/kubernetes#61446)) and with containerized kubelets ([#61456](kubernetes/kubernetes#61456)). The workaround for this issue is to specify the complete path in the hostPath volume.

Bradamant3

A couple of comments that I hope can help wrangle the PV/PVC issue. If we don't hear from Michelle soon, I'll dig further.

Bradamant3 · 2018-03-26T17:10:59Z

releases/release-1.10/release-notes-draft.md

+
+This release brings additional power to both local storage and Persistent Volumes. [Mount namespace propagation](https://github.com/kubernetes/features/issues/432) allows a container to mount a volume as rslave so that host mounts can be seen inside the container, or as rshared so that mounts made inside a container can be seen by the host. [Local Ephemeral Storage Capacity Isolation](https://github.com/kubernetes/features/issues/361) makes it possible to set requests and limits on ephemeral local storage resources. In addition, you can now create [Local Persistent Storage](https://github.com/kubernetes/features/issues/121), which enables PersistentVolumes to be created with locally attached disks, and not just network volumes.
+
+On the Persistent Volumes side, this release [Prevents deletion of Persistent Volume Claims that are used by a pod](https://github.com/kubernetes/features/issues/498) and [Persistent Volumes that are bound to a Persistent Volume Claim](https://github.com/kubernetes/features/issues/499), making it impossible to delete storage that is in use by a pod. It also includes alpha support for [online resizing of PVs](https://github.com/kubernetes/features/issues/531) without disrupting existing data.


I'm pretty sure it's safe to delete this entire paragraph. NO I'M WRONG. IGNORE. FEATURE IS IN ISSUE IS DOWNGRADING. SORRY.

correct. these features are still in

Bradamant3 · 2018-03-26T17:13:33Z

releases/release-1.10/release-notes-draft.md

+
+* Add windows config to Kubelet CRI so that WindowsContainerResources can be managed. ([#57076](https://github.com/kubernetes/kubernetes/pull/57076), [@feiskyer](https://github.com/feiskyer))
+
+* PersistentVolumes that are bound to a PersistentVolumeClaim will not be deleted. ([#58743](https://github.com/kubernetes/kubernetes/pull/58743), [@NickrenREN](https://github.com/NickrenREN))


Also pretty sure this one is out. ALSO PRETTY SURE I'M WRONG HERE. so very sorry :-(

feature is still in

msau42 · 2018-03-26T17:32:52Z

releases/release-1.10/release-notes-draft.md

+
+# Before Upgrading
+
+* In-place node upgrades to this release from versions 1.7.14, 1.8.9, and 1.9.4 are not supported if using subpath volumes with PVCs.  Such pods should be drained from the node first.


Do you need to reference kubernetes/kubernetes#61518 here?

msau42 · 2018-03-26T17:34:09Z

releases/release-1.10/release-notes-draft.md

+
+This section is still in flux.  Please make sure all issues are documented in the known Issue accumulator: [https://github.com/kubernetes/kubernetes/issues/59764](https://github.com/kubernetes/kubernetes/issues/59764)
+
+* Use of subPath module with hostPath volumes can cause issues during reconstruction ([#61446](https://github.com/kubernetes/kubernetes/issues/61446)) and with containerized kubelets ([#61456](https://github.com/kubernetes/kubernetes/issues/61456)). The workaround for this issue is to specify the complete path in the hostPath volume.


The workaround for this issue is to not use subPath with hostPath volumes and specify the complete path in the hostPath volume.

There are a few more subpath issues. Should we document those as known issues too? @liggitt @gnufied
kubernetes/kubernetes#61377: special types of files, such as unix sockets, cannot be mounted via subPath
kubernetes/kubernetes#61545: subpath mounts nested within atomic writer volumes (configmap, secret, downwardAPI, projected) do not work

Are there workarounds for these, or are we fixing them later?

We also need something like this somewhere in known issues:
If you need to downgrade from version 1.10 to version 1.9, make sure that you downgrade to version 1.9.6. Otherwise, PersistentVolume and PersistentVolumeClaim objects might not be properly deleted.

And if you want an issue to link to: kubernetes/kubernetes#60764

msau42 · 2018-03-26T18:08:12Z

@nickchase where is the question about the volume resize feature? @gnufied can help clarify what needs to be documented for 1.10

tpepper · 2018-03-26T20:20:12Z

releases/release-1.10/release-notes-draft.md

+
+* MasterConfiguration manifiest The criSocket flag is now usable within the MasterConfiguration and NodeConfiguration manifest files that exist for configuring kubeadm. Before it only existed as a command line flag and was not able to be configured when using the --config flag and the manifest files. ([#59057](https://github.com/kubernetes/kubernetes/pull/59057)([#59292](https://github.com/kubernetes/kubernetes/pull/59292), [@JordanFaust](https://github.com/JordanFaust))
+
+* `kubeadm init` can now omit the tainting of the master node if configured to do so in `kubeadm.yaml` using noTaintMaster: true. For example, uses can create a file with the content:


consider backticking the "noTaintMaster: true" in this sentence

tpepper · 2018-03-26T20:36:08Z

releases/release-1.10/release-notes-draft.md

+
+* Fixed controller manager crash when using mixed-case names in a vSphere cloud provider environment. ([#57286](https://github.com/kubernetes/kubernetes/pull/57286), [@rohitjogvmw](https://github.com/rohitjogvmw))
+
+* Flexvolume is now [enabled on Windows nodes](https://github.com/andyzhangx/Demo/tree/master/windows/flexvolume). ([#56921](https://git


double bullet is rendered here

jberkus · 2018-03-26T20:36:32Z

releases/release-1.10/release-notes-draft.md

+
+* Get windows kernel version directly from registry rather than windows.getVersion(). ([#58498](https://github.com/kubernetes/kubernetes/pull/58498), [@feiskyer](https://github.com/feiskyer))
+
+* Fixed controller manager crash when using mixed-case names in a vSphere cloud provider enviro


is fluentd-gcp-addon supposed to be a link?

no longer here

jberkus · 2018-03-26T20:37:19Z

releases/release-1.10/release-notes-draft.md

+
+* Get windows kernel version directly from registry rather than windows.getVersion(). ([#58498](https://github.com/kubernetes/kubernetes/pull/58498), [@feiskyer](https://github.com/feiskyer))
+
+* Fixed controller manager crash when using mixed-case names in a vSphere cloud provider enviro


jberkus · 2018-03-26T20:39:40Z

releases/release-1.10/release-notes-draft.md

+
+* Get windows kernel version directly from registry rather than windows.getVersion(). ([#58498](https://github.com/kubernetes/kubernetes/pull/58498), [@feiskyer](https://github.com/feiskyer))
+
+* Fixed controller manager crash when using mixed-case names in a vSphere cloud provider enviro


These two items above are confusing and I don't think either represents the final state of 1.10. Will dig into it via sig-release.

I suggest removing both of these items, since the final version is 3.1.12 and there's no point in release noting stuff that was rolled back.

I believe we ended at 3.1.12, eg:

https://github.com/kubernetes/kubernetes/blob/release-1.10/hack/lib/etcd.sh#L19
https://github.com/kubernetes/kubernetes/blob/release-1.10/build/root/WORKSPACE#L22

kubernetes/kubernetes#60998

other people did it better :-)

jberkus · 2018-03-26T20:44:52Z

releases/release-1.10/release-notes-draft.md

+
+* Get windows kernel version directly from registry rather than windows.getVersion(). ([#58498](https://github.com/kubernetes/kubernetes/pull/58498), [@feiskyer](https://github.com/feiskyer))
+
+* Fixed controller manager crash when using mixed-case names in a vSphere cloud provider enviro


remove brackets [GCE]

jberkus · 2018-03-26T20:47:28Z

releases/release-1.10/release-notes-draft.md

+
+* Get windows kernel version directly from registry rather than windows.getVersion(). ([#58498](https://github.com/kubernetes/kubernetes/pull/58498), [@feiskyer](https://github.com/feiskyer))
+
+* Fixed controller manager crash when using mixed-case names in a vSphere cloud provider enviro


jberkus · 2018-03-26T20:48:32Z

releases/release-1.10/release-notes-draft.md

+
+* Get windows kernel version directly from registry rather than windows.getVersion(). ([#58498](https://github.com/kubernetes/kubernetes/pull/58498), [@feiskyer](https://github.com/feiskyer))
+
+* Fixed controller manager crash when using mixed-case names in a vSphere cloud provider enviro


remove feat()

do you mean getVersion()?

dims · 2018-03-26T20:49:01Z

releases/release-1.10/release-notes-draft.md

-The dashboard add-on has been updated to v1.8.3, as compared to 1.8.0 in v1.9. ([#517326](https://github.com/kubernetes/kubernetes/pull/57326))
-Heapster has is the same as v1.9: v1.5.0. It will be upgraded in v1.11. ([ref](https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/cluster-monitoring/google/heapster-controller.yaml))
-Cluster Autoscaler has been updated to v1.2.0. ([#60842](https://github.com/kubernetes/kubernetes/pull/60842), [@mwielgus](https://github.com/mwielgus))
+* The supported etcd server version is 3.1.12, as compared to 3.0.170 in v1.9 ([#60988](https://github.com/kubernetes/kubernetes/pull/60988))


3.0.170 should be 3.0.17 (typo)

calebamiles · 2018-03-26T21:10:59Z

releases/release-1.10/release-notes-draft.md

+
+* Get windows kernel version directly from registry rather than windows.getVersion(). ([#58498](https://github.com/kubernetes/kubernetes/pull/58498), [@feiskyer](https://github.com/feiskyer))
+
+* Fixed controller manager crash when using mixed-case names in a vSphere cloud provider enviro


still have COS information which is only relevant for GCP

Random-Liu · 2018-03-26T21:19:43Z

releases/release-1.10/release-notes-draft.md

+* Fixed `etcd-version-monitor` to backward compatibly support etcd 3.1 [go-grpc-prometheus](https://github.com/grpc-ecosystem/go-grpc-prometheus) metrics format. ([#56871](https://github.com/kubernetes/kubernetes/pull/56871), [@jpbetz](https://github.com/jpbetz))
+
+### Node
+


Please add a summary of updates of all CRI containers.

* Container Runtime * [beta] [cri-tools](https://github.com/kubernetes-incubator/cri-tools): CLI and validation tools for CRI is now v1.0.0-beta.0. This release mainly focused on UX improvements. [@feiskyer] * [stable] [containerd](https://github.com/containerd/containerd): containerd v1.1 natively supports CRI v1alpha2 now. User can use Kubernetes v1.10, with containerd v1.1 directly, without having to use the intermediate cri-containerd daemon. [All Kubernetes 1.10 tests passed](https://k8s-testgrid.appspot.com/sig-node-containerd). [@Random-Liu] * [stable] [cri-o](https://github.com/kubernetes-incubator/cri-o): cri-o v1.10 updated CRI version to v1alpha2 and made several bug and stability fixes. [@mrunalp] * [stable] [frakti](https://github.com/kubernetes/frakti): frakti v1.10 implemented GCE Persistent Disk as high performance volume, fixed several bugs, added ARM64 support, and passed all CRI validation conformance tests and node e2e conformance tests. [@resouer]

If this is complete, I'll add it. If not, then you will need to provide me with information for me to add it, as I cannot come up with this right now.

This is complete. :)

@nickchase this addition didn't make it in your latest push

tpepper · 2018-03-26T21:42:57Z

/lgtm

calebamiles · 2018-03-26T21:48:51Z

/approve

calebamiles · 2018-03-26T21:49:42Z

/lgtm

k8s-ci-robot · 2018-03-26T21:49:50Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: calebamiles, nickchase, tpepper

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

~~OWNERS~~ [calebamiles]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Initial version of release notes markdown

362bd2a

k8s-ci-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Mar 24, 2018

k8s-ci-robot assigned calebamiles and jdumars Mar 24, 2018

calebamiles reviewed Mar 24, 2018

View reviewed changes

calebamiles suggested changes Mar 24, 2018

View reviewed changes

calebamiles added this to the v1.10 milestone Mar 24, 2018

liggitt reviewed Mar 24, 2018

View reviewed changes

k8s-ci-robot added the sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. label Mar 24, 2018

jdumars reviewed Mar 25, 2018

View reviewed changes

nikhita reviewed Mar 25, 2018

View reviewed changes

Fixed various comments in PR

a6d5acd

k8s-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Mar 25, 2018

dixudx reviewed Mar 26, 2018

View reviewed changes

feiskyer reviewed Mar 26, 2018

View reviewed changes

nickchase added 3 commits March 26, 2018 12:31

Removed debug containers, one duplicate

d857bb4

Removed "possibly missing Cherry-Picks/Watch List"

b31c6cf

Moved 61411/61412 (DaemonSets) to Known Issues.

Bradamant3 reviewed Mar 26, 2018

View reviewed changes

Added known issues

b54a303

msau42 reviewed Mar 26, 2018

View reviewed changes

nickchase added 2 commits March 26, 2018 14:21

External dependencies in progress

549afb0

Merge branch 'master' into patch-1

333ae91

tpepper reviewed Mar 26, 2018

View reviewed changes

jberkus reviewed Mar 26, 2018

View reviewed changes

calebamiles previously approved these changes Mar 26, 2018

View reviewed changes

jberkus reviewed Mar 26, 2018

View reviewed changes

dims reviewed Mar 26, 2018

View reviewed changes

calebamiles reviewed Mar 26, 2018

View reviewed changes

Fixed typos

3fdf7b0

Random-Liu reviewed Mar 26, 2018

View reviewed changes

nickchase added 5 commits March 26, 2018 17:28

miscellaneous

ae97f9c

Removed confusing etcd info.

f4eea8a

typo..

f921ecc

Update release-notes-draft.md

0d660e4

formatting

3e821ff

k8s-ci-robot assigned tpepper Mar 26, 2018

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 26, 2018

k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 26, 2018

Merge branch 'master' into patch-1

b35b3e4

k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 26, 2018

k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 26, 2018

k8s-ci-robot merged commit 0906b8d into kubernetes:master Mar 26, 2018


		This will will be used to track release notes for Kubernetes 1.10.
		[[TOC]]


		### Sig-node

		Control also figures into changes within SIG-Node, with the beta release of [Dynamic Kubelet Configuration](https://github.com/kubernetes/features/issues/281), the ability to make changes to Kubelet without having to bring down the node, and alpha support for the ability to [configure whether containers in a pod should share a single process namespace](https://github.com/kubernetes/features/issues/495), The CRI has also seen some improvements, with support for [support for Windows Container Configuration](https://github.com/kubernetes/features/issues/547) and the beta release of the [CRI validation test suite](https://github.com/kubernetes/features/issues/292). In addition, this release includes alpha support for [Debug Containers](https://github.com/kubernetes/features/issues/277).


		Control also figures into changes within SIG-Node, with the beta release of [Dynamic Kubelet Configuration](https://github.com/kubernetes/features/issues/281), the ability to make changes to Kubelet without having to bring down the node, and alpha support for the ability to [configure whether containers in a pod should share a single process namespace](https://github.com/kubernetes/features/issues/495), The CRI has also seen some improvements, with support for [support for Windows Container Configuration](https://github.com/kubernetes/features/issues/547) and the beta release of the [CRI validation test suite](https://github.com/kubernetes/features/issues/292). In addition, this release includes alpha support for [Debug Containers](https://github.com/kubernetes/features/issues/277).

		The Resource Management Working Group graduated three features to Beta in the 1.10 release. First, [CPU Manager](https://kubernetes.io/docs/tasks/administer-cluster/cpu-management-policies/), which allows users to request exclusive CPU cores. This helps performance in a variety of use-cases, including network latency sensitive applications, as well as applications that benefit from CPU cache residency. Next, [Huge Pages](https://kubernetes.io/docs/tasks/manage-hugepages/scheduling-hugepages/), which allows pods to consume either 2Mi or 1Gi Huge Pages. This benefits applications that consume large amounts of memory. Use of Huge Pages is a common tuning recommendation for databases and JVMs. Finally, the [Device Plugin](https://kubernetes.io/docs/concepts/cluster-administration/device-plugins/) feature, which provides a framework for vendors to advertise their resources to the Kubelet without changing Kubernetes core code. Targeted devices include GPUs, High-performance NICs, FPGAs, InfiniBand, and other similar computing resources that may require vendor specific initialization and setup.


		* Volume metrics support for vSphere Cloud Provider has been added. You can now monitor available space, capacity, and used space on volumes created using vSphere. ([#59328](https://github.com/kubernetes/kubernetes/pull/59328), [@divyenpatel]([https://github.com/divyenpatel](https://github.com/divyenpatel)))

		* Emit number of bound and unbound persistent volumes as Metrics. This PR adds four kinds of Volume Metrics for kube-controller-manager: bound PVC numbers, unbound PVC numbers, bound PV numbers and unbound PV numbers. The PVC metrics use namespace as dimension and the PV metrics use Sto


		([#57613](https://github.com/kubernetes/kubernetes/pull/57613), [@mtaufen]([https://github.com/mtaufen](https://github.com/mtaufen)))

		* The boostrapped RBAC role and rolebinding for the `cloud-provider` service account is now deprecated. If you're currently using this service account, you must create and apply your own [RBAC polic](https://kubernetes.io/docs/admin/authorization/rbac/)[y](https://kubernetes.io/docs/admin/authorization/rbac/) for new clusters. ([#59949](https://github.com/kubernetes/kubernetes/pull/59949), [@nicksardo]([https://github.com/nicksardo](https://github.com/nicksardo)))

		This section is still in flux. Please make sure all issues are documented in the known Issue accumulator: [https://github.com/kubernetes/kubernetes/issues/59764](https://github.com/kubernetes/kubernetes/issues/59764)

		# Deprecations


		* In-place node upgrades to this release from versions 1.7.14, 1.8.9, and 1.9.4 are not supported if using subpath volumes with PVCs. Such pods should be drained from the node first.

		* The Container Runtime Interface (CRI) version has increased from v1alpha1 to v1alpha2. Runtimes implementing the CRI will need to update to the new version, which configures container namespaces using an enumeration rather than booleans. This change to the alpha API is not backwards compatible; implementations of the CRI such as containerd, will need to update to the new API version. ([#58973](https://github.com/kubernetes/kubernetes/pull/58973), [@verb]([https://github.com/verb](https://github.com/verb)))


		KubeProxyConfiguration Before:

		apiVersion: kubeproxy.config.k8s.io/v1alpha1


		* `kubectl scale` can now scale any resource (kube, CRD, aggregate) conforming to the standard scale endpoint ([#58298](https://github.com/kubernetes/kubernetes/pull/58298), [@p0lyn0mial](https://github.com/p0lyn0mial))

		* Cluster Autoscaler has been updated to Version 1.2.0, which includes fixes around GPUs and base image change. See [https://github.com/kubernetes/autoscaler/releases/tag/cluster-autoscaler-](https://github.com/kubernetes/autoscaler/rel


		### Node

		Many of the changes within SIG-Node revolve around control, with the beta release of [Dynamic Kubelet Configuration](https://github.com/kubernetes/features/issues/281), the ability to make changes to Kubelet without having to bring down the node, and alpha support for the ability to [configure whether containers in a pod should share a single process namespace](https://github.com/kubernetes/features/issues/495), The CRI has also seen some improvements, with support for [support for Windows Container Configuration](https://github.com/kubernetes/features/issues/547) and the beta release of the [CRI validation test suite](https://github.com/kubernetes/features/issues/292). In addition, this release includes alpha support for [Debug Containers](https://github.com/kubernetes/features/issues/277).


		This release brings additional power to both local storage and Persistent Volumes. [Mount namespace propagation](https://github.com/kubernetes/features/issues/432) allows a container to mount a volume as rslave so that host mounts can be seen inside the container, or as rshared so that mounts made inside a container can be seen by the host. [Local Ephemeral Storage Capacity Isolation](https://github.com/kubernetes/features/issues/361) makes it possible to set requests and limits on ephemeral local storage resources. In addition, you can now create [Local Persistent Storage](https://github.com/kubernetes/features/issues/121), which enables PersistentVolumes to be created with locally attached disks, and not just network volumes.

		On the Persistent Volumes side, this release [Prevents deletion of Persistent Volume Claims that are used by a pod](https://github.com/kubernetes/features/issues/498) and [Persistent Volumes that are bound to a Persistent Volume Claim](https://github.com/kubernetes/features/issues/499), making it impossible to delete storage that is in use by a pod. It also includes alpha support for [online resizing of PVs](https://github.com/kubernetes/features/issues/531) without disrupting existing data.


		* Add windows config to Kubelet CRI so that WindowsContainerResources can be managed. ([#57076](https://github.com/kubernetes/kubernetes/pull/57076), [@feiskyer](https://github.com/feiskyer))

		* PersistentVolumes that are bound to a PersistentVolumeClaim will not be deleted. ([#58743](https://github.com/kubernetes/kubernetes/pull/58743), [@NickrenREN](https://github.com/NickrenREN))


		# Before Upgrading

		* In-place node upgrades to this release from versions 1.7.14, 1.8.9, and 1.9.4 are not supported if using subpath volumes with PVCs. Such pods should be drained from the node first.


		* MasterConfiguration manifiest The criSocket flag is now usable within the MasterConfiguration and NodeConfiguration manifest files that exist for configuring kubeadm. Before it only existed as a command line flag and was not able to be configured when using the --config flag and the manifest files. ([#59057](https://github.com/kubernetes/kubernetes/pull/59057)([#59292](https://github.com/kubernetes/kubernetes/pull/59292), [@JordanFaust](https://github.com/JordanFaust))

		* `kubeadm init` can now omit the tainting of the master node if configured to do so in `kubeadm.yaml` using noTaintMaster: true. For example, uses can create a file with the content:


		* Fixed controller manager crash when using mixed-case names in a vSphere cloud provider environment. ([#57286](https://github.com/kubernetes/kubernetes/pull/57286), [@rohitjogvmw](https://github.com/rohitjogvmw))

		* Flexvolume is now [enabled on Windows nodes](https://github.com/andyzhangx/Demo/tree/master/windows/flexvolume). ([#56921](https://git


		* Get windows kernel version directly from registry rather than windows.getVersion(). ([#58498](https://github.com/kubernetes/kubernetes/pull/58498), [@feiskyer](https://github.com/feiskyer))

		* Fixed controller manager crash when using mixed-case names in a vSphere cloud provider enviro

		* Fixed `etcd-version-monitor` to backward compatibly support etcd 3.1 [go-grpc-prometheus](https://github.com/grpc-ecosystem/go-grpc-prometheus) metrics format. ([#56871](https://github.com/kubernetes/kubernetes/pull/56871), [@jpbetz](https://github.com/jpbetz))

		### Node

Initial version of release notes markdown #92

Initial version of release notes markdown #92

Conversation

nickchase commented Mar 24, 2018

dims commented Mar 24, 2018

Choose a reason for hiding this comment

Choose a reason for hiding this comment

calebamiles left a comment • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Bradamant3 left a comment

Choose a reason for hiding this comment

Bradamant3 Mar 26, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Bradamant3 Mar 26, 2018 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Bradamant3 Mar 26, 2018 • edited Loading

Choose a reason for hiding this comment

msau42 commented Mar 26, 2018

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tpepper commented Mar 26, 2018

calebamiles commented Mar 26, 2018

calebamiles commented Mar 26, 2018

k8s-ci-robot commented Mar 26, 2018

calebamiles left a comment •

edited

Loading

Bradamant3 Mar 26, 2018 •

edited

Loading

Bradamant3 Mar 26, 2018 •

edited

Loading

Bradamant3 Mar 26, 2018 •

edited

Loading