Final 1.13 release notes, copied in from Google Doc #386

marpaia · 2018-11-28T20:44:40Z

This PR updates the release-notes-draft.md file for the 1.13 release to contain the "final" set of release notes. This document should (correct me if I'm wrong please) get copied into the CHANGELOG-1.13.md file in k/k by anago when the 1.13.0 tag is cut (CC: @dougm and @tpepper for confirmation).

/assign @AishSundar

dougm

@marpaia yes: relnotes from the release repo will use it if it exists: https://github.com/kubernetes/release/blob/4a45486346c3a2f345caefaba23be2f904d6dbc0/relnotes#L376-L377

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

+## Known Issues
+
+- If kubelet plugin registration for a driver fails, kubelet will not retry. The driver must delete and recreate the driver registration socket in order to force kubelet to attempt registration again. Restarting only the driver container may not be sufficient to trigger recreation of the socket, instead a pod restart may be required. ([#71487](https://github.com/kubernetes/kubernetes/issues/71487))
+- In come cases, a PVC may have erroneous Resizing condition even after volume has been successfully expanded. Users may choose to delete the condition, but it is not required.


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


-### SIG CLI, and SIG Testing
+SIG Node focused on stability and performance improvements in the 1.13 release. A new alpha feature is introduced to improve the mechanism that nodes heartbeat back to the control plane. The `NodeLease` feature results in the node using a `Lease` resource in the `kube-node-lease` namespace that is renewed periodically. The `NodeStatus` that was used previously to heartbeat back to the control plane is only updated when it changes. This reduces load on the control plane for large clusters.


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

+* Implement support for storage class parameter - volume type ([#73](https://github.com/kubernetes-sigs/aws-ebs-csi-driver/pull/73), [@leakingtapan](https://github.com/leakingtapan/))
+* Implement support for storage class parameter - fsType ([#67](https://github.com/kubernetes-sigs/aws-ebs-csi-driver/pull/67), [@leakingtapan](https://github.com/leakingtapan/))
+* Added missing capability and clusterrole permission to enable tology awareness scheduling ([2873e0b](https://github.com/kubernetes-sigs/aws-ebs-csi-driver/commit/2873e0b), [@leakingtapan](https://github.com/leakingtapan/))
+* Wait for correct attachment state ([f11db6c](https://github.com/kubernetes-sigs/aws-ebs-csi-driver/commit/f11db6c), [@bert


saad-ali · 2018-11-28T21:00:55Z

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


- Scheduling conformance tests related to daemonsets should set the annotation that relaxes node selection restrictions, if any are set. This ensures conformance tests can run on a wider array of clusters. ([#68793](https://github.com/kubernetes/kubernetes/pull/68793), [@aveshagarwal](https://github.com/aveshagarwal))
+#### aws-ebs-csi-driver v0.1.0-alpha.1


All of these are changes to an external CSI driver https://github.com/kubernetes-sigs/aws-ebs-csi-driver. They are not part of the Kubernetes 1.13 release.

Please remove all references to aws-ebs-csi-driver.

Adding in @d-nishi and @AishSundar as we had a chat about whether or not this was appropriate for the release notes. I'll note that there was a similar conversation on notes for kubeadm vs kops/kubespray/etc and it was asserted that since kubeadm is apart of the release artifacts for a Kubernetes release, it's appropriate to include them in the notes.

CSI drivers are currently not shipped as part of Kubernetes. The release cadence of external CSI drivers doesn't necessarily align with Kubernetes releases. So it really makes no sense to include release notes of a CSI driver here at this point.

The release notes already link to https://kubernetes-csi.github.io/docs/Drivers.html where folks can find a list of drivers.

@saad-ali -- this is not just about CSI driver. It is about all sub-projects that sit in k8s-sigs and are out-of-tree but work with k8s. We discussed this at the very beginning of the release cycle. Sub-projects under k8s-sigs though out of tree, benefit from being tagged to a specific k8s release because we add CI signal before moving the project from alpha, beta to GA. This discipline makes it possible for users to know which k8s version to test the driver with atleast in AWS. we pegged the aws-ebs-csi-driver to k8s 1.13 for all testing.

Adding @justaugustus to lend some color to the discussion we had around release notes mention for out-of-tree projects.

Hey y'all (@d-nishi, @saad-ali, @AishSundar, et al), I took a run at adding a paragraph to SIG AWS's Major Themes which links to the documentation for each of these external projects: 997ba6a.

What do y'all think about this? IMO it definitely makes the notes a lot easier to parse as there isn't a big block of sections with 6 levels of headers.

@marpaia - sent you an email with some wording change but linked to release notes of the subprojects. please use the same - Cheers!

resolved this with @marpaia with suggested Option (b) aka linked to subproject changelogs and reduced the description to one paragraph.

Thanks all, I know this is new territory. We will have more of this as the project components get looser coupling. I didn't mean to imply any procedural mistakes or ill intent.

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

+- kubeadm: Added a `v1beta1` API. ([#69289](https://github.com/kubernetes/kubernetes/pull/69289), [@fabriziopandini](https://github.com/fabriziopandini))
+- kubectl: support multiple arguments for cordon/uncordon and drain ([#68655](https://github.com/kubernetes/kubernetes/pull/68655), [@goodluckbot](https://github.com/goodluckbot))
+- kubeadm: UnifiedControlPlaneImage is replaced by UseHyperKubeImage boolean value. ([#70793](https://github.com/kubernetes/kubernetes/pull/70793), [@rosti](https://github.com/rosti))
+- kubeadm v1beta1 API: InitConfiguration.APIEndpoint has been renamed to .LocalAPIEndpoint ([#70761](https://github.com/kubernetes/kubernetes/pull/70761), [@luxas](https://github.com/luxas))


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

- kubeadm: Add a `v1beta1` API. ([#69289](https://github.com/kubernetes/kubernetes/pull/69289), [@fabriziopandini](https://github.com/fabriziopandini))
+- kubeadm: Added a `v1beta1` API. ([#69289](https://github.com/kubernetes/kubernetes/pull/69289), [@fabriziopandini](https://github.com/fabriziopandini))
+- kubectl: support multiple arguments for cordon/uncordon and drain ([#68655](https://github.com/kubernetes/kubernetes/pull/68655), [@goodluckbot](https://github.com/goodluckbot))
+- kubeadm: UnifiedControlPlaneImage is replaced by UseHyperKubeImage boolean value. ([#70793](https://github.com/kubernetes/kubernetes/pull/70793), [@rosti](https://github.com/rosti))


liggitt · 2018-11-28T22:04:23Z

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

+- The `node.status.volumes.attached.devicePath` field is deprecated for CSI volumes and will not be set in future releases ([#71095](https://github.com/kubernetes/kubernetes/pull/71095), [@msau42](https://github.com/msau42))
+- kubectl
+ - The `kubectl convert` command is deprecated and will be removed in a future release ([#70820](https://github.com/kubernetes/kubernetes/pull/70820), [@seans3](https://github.com/seans3))
+- Support for passing unknown provider names to the E2E test binaries is deprecated and will be removed in a future release. Use `--provider=skeleton` (no ssh access) or `--provider=local` (local cluster with ssh) instead. ([#70141](https://github.com/kubernetes/kubernetes/pull/70141), [@pohly](https://github.com/pohly))

 ## API Changes


@kubernetes/sig-cluster-lifecycle-pr-reviews are all the kubeadm API changes listed below limited to the v1beta1 config file API? if so, would it make more sense to point the single "added v1beta1 API" item to documentation of the config file format, rather than a list of "changes" to an API that is new in 1.13?

some are new features @fabriziopandini @timothysc

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

+ - The deprecated command `run-container` has been removed. Invocations should use `kubectl run` instead ([#70728](https://github.com/kubernetes/kubernetes/pull/70728), [@Pingan2017](https://github.com/Pingan2017))
+- client-go releases will no longer have bootstrap (k8s.io/client-go/tools/bootstrap) related code. any reference to it will break. Please redirect all references to k8s.io/bootstrap instead. ([#67356](https://github.com/kubernetes/kubernetes/pull/67356), [@yliaog](https://github.com/yliaog))
+
+## Known Issues


AishSundar · 2018-11-28T22:07:34Z

Thanks @marpaia. I left a comment. feel free to remove the hold when ready

/lgtm
/hold

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


-### SIG Apps, SIG Storage, and SIG Testing
+With this release we've made several important enhancements to core SIG-Auth areas. In the authorization category, we've further reduced Kubelet privileges by restricting node self-updates of labels to a whitelisted selection and by disallowing kubelets from deleting their Node API object. In authentication, we added alpha-level support for automounting improved service account tokens through projected volumes. We also enabled audience validation in TokenReview for the new tokens for improved scoping. Under audit logging, the new alpha-level "dynamic audit configuration" adds support for dynamically registering webhooks to receive a stream of audit events. Finally, we've enhanced secrets protection by graduating etcd encryption out of experimental.


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

+
+- If kubelet plugin registration for a driver fails, kubelet will not retry. The driver must delete and recreate the driver registration socket in order to force kubelet to attempt registration again. Restarting only the driver container may not be sufficient to trigger recreation of the socket, instead a pod restart may be required. ([#71487](https://github.com/kubernetes/kubernetes/issues/71487))
+- In come cases, a PVC may have erroneous Resizing condition even after volume has been successfully expanded. Users may choose to delete the condition, but it is not required.
+


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

 - kubeadm: JoinConfiguration now houses the discovery options in a nested Discovery structure, which in turn has a couple of other nested structures to house more specific options (BootstrapTokenDiscovery and FileDiscovery) ([#67763](https://github.com/kubernetes/kubernetes/pull/67763), [@rosti](https://github.com/rosti))
- kubeadm: Add a `v1beta1` API. ([#69289](https://github.com/kubernetes/kubernetes/pull/69289), [@fabriziopandini](https://github.com/fabriziopandini))
+- kubeadm: Added a `v1beta1` API. ([#69289](https://github.com/kubernetes/kubernetes/pull/69289), [@fabriziopandini](https://github.com/fabriziopandini))


justaugustus · 2018-11-29T01:23:27Z

/assign

xiangpengzhao

some nits.

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

+- kube-scheduler dropped support for configuration files with apiVersion `componentconfig/v1alpha1`. Ensure kube-scheduler is configured using command-line flags or a configuration file with apiVersion `kubescheduler.config.k8s.io/v1alpha1` before upgrading to 1.13.
+- kubectl
+ - The deprecated command `run-container` has been removed. Invocations should use `kubectl run` instead ([#70728](https://github.com/kubernetes/kubernetes/pull/70728), [@Pingan2017](https://github.com/Pingan2017))
+- client-go releases will no longer have bootstrap (k8s.io/client-go/tools/bootstrap) related code. any reference to it will break. Please redirect all references to k8s.io/bootstrap instead. ([#67356](https://github.com/kubernetes/kubernetes/pull/67356), [@yliaog](https://github.com/yliaog))


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

+ - The `--experimental-encryption-provider-config` flag is deprecated in favor of `--encryption-provider-config`. The old flag is accepted with a warning but will be removed in 1.14. ([#71206](https://github.com/kubernetes/kubernetes/pull/71206), [@stlaz](https://github.com/stlaz))
+ - The `--deserialization-cache-size` flag is deprecated, and will be removed in a future release. The flag is inactive since the etcd2 storage backend was removed. ([#69842](https://github.com/kubernetes/kubernetes/pull/69842), [@liggitt](https://github.com/liggitt))
+ - The `Node` authorization mode no longer allows kubelets to delete their Node API objects (prior to 1.11, in rare circumstances related to cloudprovider node ID changes, kubelets would attempt to delete/recreate their Node object at startup) ([#71021](https://github.com/kubernetes/kubernetes/pull/71021), [@liggitt](https://github.com/liggitt))
+ - The built-in `system:csi-external-provisioner` and `system:csi-external-attacher` cluster roles are deprecated and will not be auto-created in a future release. CSI deployments should provide their own RBAC role definitions with required permissions. ([#69868](https://github.com/kubernetes/kubernetes/pull/69868))


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

+ - The `--deserialization-cache-size` flag is deprecated, and will be removed in a future release. The flag is inactive since the etcd2 storage backend was removed. ([#69842](https://github.com/kubernetes/kubernetes/pull/69842), [@liggitt](https://github.com/liggitt))
+ - The `Node` authorization mode no longer allows kubelets to delete their Node API objects (prior to 1.11, in rare circumstances related to cloudprovider node ID changes, kubelets would attempt to delete/recreate their Node object at startup) ([#71021](https://github.com/kubernetes/kubernetes/pull/71021), [@liggitt](https://github.com/liggitt))
+ - The built-in `system:csi-external-provisioner` and `system:csi-external-attacher` cluster roles are deprecated and will not be auto-created in a future release. CSI deployments should provide their own RBAC role definitions with required permissions. ([#69868](https://github.com/kubernetes/kubernetes/pull/69868))
+ - The built-in `system:aws-cloud-provider` cluster role is deprecated and will not be auto-created in a future release. Deployments using the AWS cloud provider should grant required permissions to the `aws-cloud-provider` service account in the `kube-system` namespace as part of deployment. ([#66635](https://github.com/kubernetes/kubernetes/pull/66635))


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

+ - The built-in `system:csi-external-provisioner` and `system:csi-external-attacher` cluster roles are deprecated and will not be auto-created in a future release. CSI deployments should provide their own RBAC role definitions with required permissions. ([#69868](https://github.com/kubernetes/kubernetes/pull/69868))
+ - The built-in `system:aws-cloud-provider` cluster role is deprecated and will not be auto-created in a future release. Deployments using the AWS cloud provider should grant required permissions to the `aws-cloud-provider` service account in the `kube-system` namespace as part of deployment. ([#66635](https://github.com/kubernetes/kubernetes/pull/66635))
+- kubelet
+ - Use of the beta plugin registration directory `{kubelet_root_dir}/plugins/` for registration of external drivers via the kubelet plugin registration protocol is deprecated in favor of `{kubelet_root_dir}/plugins_registry/`. Support for the old directory is planned to be removed in v1.15. Device plugin and CSI storage drivers should switch to the new directory prior to v1.15. Only CSI storage drivers that support 0.x versions of the CSI API are allowed in the old directory. ([#70494](https://github.com/kubernetes/kubernetes/pull/70494), [#71314](https://github.com/kubernetes/kubernetes/pull/71314))


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

+ - The built-in `system:aws-cloud-provider` cluster role is deprecated and will not be auto-created in a future release. Deployments using the AWS cloud provider should grant required permissions to the `aws-cloud-provider` service account in the `kube-system` namespace as part of deployment. ([#66635](https://github.com/kubernetes/kubernetes/pull/66635))
+- kubelet
+ - Use of the beta plugin registration directory `{kubelet_root_dir}/plugins/` for registration of external drivers via the kubelet plugin registration protocol is deprecated in favor of `{kubelet_root_dir}/plugins_registry/`. Support for the old directory is planned to be removed in v1.15. Device plugin and CSI storage drivers should switch to the new directory prior to v1.15. Only CSI storage drivers that support 0.x versions of the CSI API are allowed in the old directory. ([#70494](https://github.com/kubernetes/kubernetes/pull/70494), [#71314](https://github.com/kubernetes/kubernetes/pull/71314))
+ - With the release of the CSI 1.0 API, support for CSI drivers using 0.3 and older releases of the CSI API is deprecated, and is planned to be removed in Kubernetes v1.15. CSI drivers should be updated to support the CSI 1.0 API, and deployed in the new kubelet plugin registration directory (`{kubelet_root_dir}/plugins_registry/`) once all nodes in the cluster are at 1.13 or higher ([#71020](https://github.com/kubernetes/kubernetes/pull/71020), [#71314](https://github.com/kubernetes/kubernetes/pull/71314))


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

+- Added dns capabilities for Windows CNI plugins: ([#67435](https://github.com/kubernetes/kubernetes/pull/67435), [@feiskyer](https://github.com/feiskyer))
+- kube-apiserver: `--audit-webhook-version` and `--audit-log-version` now default to `audit.k8s.io/v1` if unspecified ([#70476](https://github.com/kubernetes/kubernetes/pull/70476), [@charrywanganthony](https://github.com/charrywanganthony))
+- kubeadm: timeoutForControlPlane is introduced as part of the API Server config, that controls the timeout for the wait for control plane to be up. Default value is 4 minutes. ([#70480](https://github.com/kubernetes/kubernetes/pull/70480), [@rosti](https://github.com/rosti))
+- --api-audiences now defaults to the --service-account-issuer if the issuer is provided but the API audience is not. ([#70308](https://github.com/kubernetes/kubernetes/pull/70308), [@mikedanese](https://github.com/mikedanese))


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


- Scheduling conformance tests related to daemonsets should set the annotation that relaxes node selection restrictions, if any are set. This ensures conformance tests can run on a wider array of clusters. ([#68793](https://github.com/kubernetes/kubernetes/pull/68793), [@aveshagarwal](https://github.com/aveshagarwal))
+#### aws-ebs-csi-driver v0.1.0-alpha.1


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

- kube-apiserver has removed support for the `etcd2` storage backend (deprecated since v1.9). Existing clusters must migrate etcd v2 data to etcd v3 storage before upgrading to v1.13. ([#69310](https://github.com/kubernetes/kubernetes/pull/69310), [@liggitt](https://github.com/liggitt))
+* Updated driver name and topology key ([#105](https://github.com/kubernetes-sigs/aws-ebs-csi-driver/pull/105), [@leakingtapan](https://github.com/leakingtapan/))
+* Added support for creating encrypted volume and unit test ([#80](https://github.com/kubernetes-sigs/aws-ebs-csi-driver/pull/80), [@leakingtapan](https://github.com/leakingtapan/))
+* Implement support for storage class parameter - volume type ([#73](https://github.com/kubernetes-sigs/aws-ebs-csi-driver/pull/73), [@leakingtapan](htt


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


- Speedup process lookup in /proc ([#66367](https://github.com/kubernetes/kubernetes/pull/66367), [@cpuguy83](https://github.com/cpuguy83))
+- kubelet --system-reserved and --kube-reserved are supported now on Windows nodes ([#69960](https://github.com/kubernetes/kubernetes/pull/69960), [@feiskyer](https://github.com/feiskyer))


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


- Speedup process lookup in /proc ([#66367](https://github.com/kubernetes/kubernetes/pull/66367), [@cpuguy83](https://github.com/cpuguy83))
+- kubelet --system-reserved and --kube-reserved are supported now on Windows nodes ([#69960](https://github.com/kubernetes/kubernetes/pull/69960), [@feiskyer](https://github.com/feiskyer))
+- Windows runtime endpoints is now switched to 'npipe:////./pipe/dockershim' from 'tcp://localhost:3735'. ([#69516](https://github.com/kubernetes/kubernetes/pull/69516), [@feiskyer](https://github.com/feiskyer))


…raph in major themes

marpaia · 2018-11-29T04:13:13Z

/hold cancel

dougm

/lgtm

k8s-ci-robot · 2018-11-29T04:15:24Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AishSundar, dougm, marpaia

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:

~~releases/release-1.13/OWNERS~~ [AishSundar]

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

AishSundar · 2018-11-29T06:15:52Z

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

+ - The built-in `system:aws-cloud-provider` cluster role is deprecated and will not be auto-created in a future release. Deployments using the AWS cloud provider should grant required permissions to the `aws-cloud-provider` service account in the `kube-system` namespace as part of deployment. ([#66635](https://github.com/kubernetes/kubernetes/pull/66635), [@wgliang](https://github.com/wgliang))
+- kubelet
+ - Use of the beta plugin registration directory `{kubelet_root_dir}/plugins/` for registration of external drivers via the kubelet plugin registration protocol is deprecated in favor of `{kubelet_root_dir}/plugins_registry/`. Support for the old directory is planned to be removed in v1.15. Device plugin and CSI storage drivers should switch to the new directory prior to v1.15. Only CSI storage drivers that support 0.x versions of the CSI API are allowed in the old directory. ([#70494](https://github.com/kubernetes/kubernetes/pull/70494) by [@RenaudWasTaken](https://github.com/RenaudWasTaken) and [#71314](https://github.com/kubernetes/kubernetes/pull/71314) by [@saad-ali](https://github.com/saad-ali))
+ - With the release of the CSI 1.0 API, support for CSI drivers using 0.3 and older releases of the CSI API is deprecated, and is planned to be removed in Kubernetes v1.15. CSI drivers should be updated to support the CSI 1.0 API, and deployed in the new kubelet plugin registration directory (`{kubelet_root_dir}/plugins_registry/`) once all nodes in the cluster are at 1.13 or higher ([#71020](https://github.com/kubernetes/kubernetes/pull/71020) and [#71314](https://github.com/kubernetes/kubernetes/pull/71314), both by [@saad-ali](https://github.com/saad-ali))


@marpaia this is no longer the case with 1.13.beta.2 build. We enabled backward compatibility in 1.13. This can be removed afaik. @saad-ali @liggitt to confirm

This is the deprecation notice. Note that no actions are required prior to upgrade, and support is planned through 1.15

@AishSundar @liggitt so we are leaving this in then, correct?

MaciekPytel · 2018-11-29T11:00:43Z

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


-## Notes from Individual SIGs
+- Updated Cluster Autoscaler version to 1.13.0-rc.2. See the [Release Notes](https://github.com/kubernetes/autoscaler/releases/tag/cluster-autoscaler-1.13.0-rc.2) for more information. ([#71452](https://github.com/kubernetes/kubernetes/pull/71452), [@losipiuk](https://github.com/losipiuk))


The version that will go out with official release is Cluster Autoscaler 1.13.0 (not -rc.2). Can we update the version and the link to release notes (to https://github.com/kubernetes/autoscaler/releases/tag/cluster-autoscaler-1.13.0)?

@MaciekPytel I updated that last night :) #387

k8s-ci-robot assigned AishSundar Nov 28, 2018

k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Nov 28, 2018

k8s-ci-robot requested review from dougm and jberkus November 28, 2018 20:44

k8s-ci-robot added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Nov 28, 2018

Final 1.13 release notes, copied in from Google Doc

fbdb5da

marpaia force-pushed the 1.13-release-notes branch from 0785145 to fbdb5da Compare November 28, 2018 20:47

marpaia mentioned this pull request Nov 28, 2018

1.13 Release Notes: "Known Issues" kubernetes/kubernetes#70955

Closed

dougm reviewed Nov 28, 2018

View reviewed changes

saad-ali suggested changes Nov 28, 2018

View reviewed changes

liggitt reviewed Nov 28, 2018

View reviewed changes

k8s-ci-robot added the sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. label Nov 28, 2018

AishSundar reviewed Nov 28, 2018

View reviewed changes

k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm "Looks good to me", indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 28, 2018

liggitt reviewed Nov 28, 2018

View reviewed changes

msau42 reviewed Nov 28, 2018

View reviewed changes

Add known issue for RePD

ccd2fee

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

marpaia added 3 commits November 28, 2018 16:52

fix typo in flex volume resize known issue

6016a34

@liggitt code review comments

5c564e6

@saad-ali's code review comments

d9d9088

timothysc suggested changes Nov 29, 2018

View reviewed changes

k8s-ci-robot assigned justaugustus Nov 29, 2018

Disperse API Changes to the relevent sections

a857eba

xiangpengzhao reviewed Nov 29, 2018

View reviewed changes

marpaia added 3 commits November 28, 2018 20:26

Remove release notes for out of tree AWS projects in favor of a parag…

997ba6a

…raph in major themes

minor copy edits

5e7b2af

@xiangpengzhao code review comments

e01266c

marpaia force-pushed the 1.13-release-notes branch from 2c1fbd2 to e01266c Compare November 29, 2018 03:41

marpaia added 2 commits November 28, 2018 21:08

@d-nishi copyedits

2649dfe

These damn MacBook keyboards

e3d3f91

k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 29, 2018

dougm reviewed Nov 29, 2018

View reviewed changes

k8s-ci-robot assigned dougm Nov 29, 2018

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

k8s-ci-robot merged commit a20cc00 into kubernetes:master Nov 29, 2018

marpaia deleted the 1.13-release-notes branch November 29, 2018 04:20

AishSundar reviewed Nov 29, 2018

View reviewed changes

MaciekPytel reviewed Nov 29, 2018

View reviewed changes

d-nishi mentioned this pull request Feb 1, 2019

Soliciting feedback: Release cadence for out-of-tree features #486

Open


		### SIG CLI, and SIG Testing
		SIG Node focused on stability and performance improvements in the 1.13 release. A new alpha feature is introduced to improve the mechanism that nodes heartbeat back to the control plane. The `NodeLease` feature results in the node using a `Lease` resource in the `kube-node-lease` namespace that is renewed periodically. The `NodeStatus` that was used previously to heartbeat back to the control plane is only updated when it changes. This reduces load on the control plane for large clusters.


		- Scheduling conformance tests related to daemonsets should set the annotation that relaxes node selection restrictions, if any are set. This ensures conformance tests can run on a wider array of clusters. ([#68793](https://github.com/kubernetes/kubernetes/pull/68793), [@aveshagarwal](https://github.com/aveshagarwal))
		#### aws-ebs-csi-driver v0.1.0-alpha.1


		### SIG Apps, SIG Storage, and SIG Testing
		With this release we've made several important enhancements to core SIG-Auth areas. In the authorization category, we've further reduced Kubelet privileges by restricting node self-updates of labels to a whitelisted selection and by disallowing kubelets from deleting their Node API object. In authentication, we added alpha-level support for automounting improved service account tokens through projected volumes. We also enabled audience validation in TokenReview for the new tokens for improved scoping. Under audit logging, the new alpha-level "dynamic audit configuration" adds support for dynamically registering webhooks to receive a stream of audit events. Finally, we've enhanced secrets protection by graduating etcd encryption out of experimental.


		- If kubelet plugin registration for a driver fails, kubelet will not retry. The driver must delete and recreate the driver registration socket in order to force kubelet to attempt registration again. Restarting only the driver container may not be sufficient to trigger recreation of the socket, instead a pod restart may be required. ([#71487](https://github.com/kubernetes/kubernetes/issues/71487))
		- In come cases, a PVC may have erroneous Resizing condition even after volume has been successfully expanded. Users may choose to delete the condition, but it is not required.


		- Speedup process lookup in /proc ([#66367](https://github.com/kubernetes/kubernetes/pull/66367), [@cpuguy83](https://github.com/cpuguy83))
		- kubelet --system-reserved and --kube-reserved are supported now on Windows nodes ([#69960](https://github.com/kubernetes/kubernetes/pull/69960), [@feiskyer](https://github.com/feiskyer))


		## Notes from Individual SIGs
		- Updated Cluster Autoscaler version to 1.13.0-rc.2. See the [Release Notes](https://github.com/kubernetes/autoscaler/releases/tag/cluster-autoscaler-1.13.0-rc.2) for more information. ([#71452](https://github.com/kubernetes/kubernetes/pull/71452), [@losipiuk](https://github.com/losipiuk))

Final 1.13 release notes, copied in from Google Doc #386

Final 1.13 release notes, copied in from Google Doc #386

Conversation

marpaia commented Nov 28, 2018

dougm left a comment

Choose a reason for hiding this comment

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

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

This comment was marked as resolved.

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

This comment was marked as resolved.

This comment was marked as resolved.

Choose a reason for hiding this comment

neolit123 Nov 28, 2018 • edited Loading

Choose a reason for hiding this comment

This comment was marked as resolved.

AishSundar commented Nov 28, 2018

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

justaugustus commented Nov 29, 2018

xiangpengzhao left a comment

Choose a reason for hiding this comment

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

This comment was marked as resolved.

marpaia commented Nov 29, 2018

dougm left a comment

Choose a reason for hiding this comment

k8s-ci-robot commented Nov 29, 2018

Choose a reason for hiding this comment

liggitt Nov 29, 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

neolit123 Nov 28, 2018 •

edited

Loading

liggitt Nov 29, 2018 •

edited

Loading