- [Cluster Lifecycle](#cluster-lifecycle)
    - [GCP](#gcp)
    - [Network](#network)
    - [Node](#node)
    - [Scheduling](#scheduling)
    - [Storage](#storage)
    - [Testing](#testing)
    - [VMware](#vmware)
    - [Windows](#windows)
  - [External Dependencies](#external-dependencies)
- [v1.14.0-rc.1](#v1140-rc1)
  - [Downloads for v1.14.0-rc.1](#downloads-for-v1140-rc1)

    val i: Iterator<String> = cache.urls()
    assertThat(i.hasNext()).isTrue()
    assertThat(i.next()).isEqualTo(urlA.toString())
    assertThat(i.hasNext()).isTrue()
    assertThat(i.next()).isEqualTo(urlB.toString())
    assertThat(i.hasNext()).isTrue()
    assertThat(i.next()).isEqualTo(urlC.toString())

    // ... and nothing else.
    assertThat(i.hasNext()).isFalse()
    assertFailsWith<NoSuchElementException> {

*.eu-west-3.airflow.amazonaws.com
*.ewp.live
*.ex.futurecms.at
*.ex.ortsinfo.at
*.experiments.sagemaker.aws
*.firenet.ch
*.fk
*.frusky.de
*.futurecms.at
*.gateway.dev
*.hosted.app
*.hosting.myjino.ru
*.hosting.ovh.net
*.id.pub
*.il-central-1.airflow.amazonaws.com
*.in.futurecms.at
*.jm
*.kawasaki.jp
*.kh
*.kin.one
*.kin.pub
*.kitakyushu.jp
*.kobe.jp
*.kunden.ortsinfo.at
*.landing.myjino.ru

- Fix invalid VMSS updates due to incorrect cache ([#89002](https://github.com/kubernetes/kubernetes/pull/89002), [@ArchangelSDY](https://github.com/ArchangelSDY)) [SIG Cloud Provider]

### SIG Scalability

[SIG Scalability][] is responsible for scalability testing, measuring and
improving system performance, and answering questions related to scalability.

For the 1.8 release, SIG Scalability focused on automating large cluster
scalability testing in a continuous integration (CI) environment. The SIG
defined a concrete process for scalability testing, created

* AWS cloudprovider plugin: Fix for large clusters (200+ nodes). Also fix bug with volumes not getting detached from a node after reboot. ([#48312](https://github.com/kubernetes/kubernetes/pull/48312), [@gnufied](https://github.com/gnufied))
* Fix Pods using Portworx volumes getting stuck in ContainerCreating phase. ([#48898](https://github.com/kubernetes/kubernetes/pull/48898), [@harsh-px](https://github.com/harsh-px))

If you experience any snags when using TF 2.0, please let us know at the
[TF 2.0 Testing User Group](https://groups.google.com/a/tensorflow.org/forum/?utm_medium=email&utm_source=footer#!forum/testing).
We have a support mailing list as well as weekly testing meetings, and would
love to hear your migration feedback and questions.

## Bug Fixes and Other Changes

*   `tf.contrib`:

*.eu-west-3.airflow.amazonaws.com
*.ewp.live
*.ex.futurecms.at
*.ex.ortsinfo.at
*.experiments.sagemaker.aws
*.firenet.ch
*.fk
*.frusky.de
*.futurecms.at
*.gateway.dev
*.hosted.app
*.hosting.myjino.ru
*.hosting.ovh.net
*.id.pub
*.il-central-1.airflow.amazonaws.com
*.in.futurecms.at
*.jm
*.kawasaki.jp
*.kh
*.kin.one
*.kin.pub
*.kitakyushu.jp
*.kobe.jp
*.kunden.ortsinfo.at
*.landing.myjino.ru

### API-machinery

* The Kubelet's deprecated `--allow-privileged` flag now defaults to true. This enables users to stop setting `--allow-privileged` in order to transition to `PodSecurityPolicy`. Previously, users had to continue setting `--allow-privileged`, because the default was false. ([#63442](https://github.com/kubernetes/kubernetes/pull/63442), [@mtaufen](https://github.com/mtaufen))