* [stable] [cri-o](https://github.com/kubernetes-incubator/cri-o): CRI implementation for OCI-based runtimes [[@mrunalp](https://github.com/mrunalp)]

  * Passed all the Kubernetes 1.7 end-to-end conformance test suites.
  * Verification against Kubernetes 1.8 is planned soon after the release.

*   [stable] [cri-o](https://github.com/kubernetes-incubator/cri-o): CRI implementation for OCI-based runtimes is now v1.9. [[@mrunalp](https://github.com/mrunalp)]
    *   Pass all the Kubernetes 1.9 end-to-end test suites and now gating PRs as well
    *   Pass all the CRI validation tests
    *   Release has been focused on bug fixes, stability and performance with runc and Clear Containers
    *   Minikube integration

- Introducing new semantic for metric `volume_operation_total_seconds` to be the end to end latency of volume provisioning/deletion. Existing metric "storage_operation_duration_seconds" will remain untouched, however it is exposed to the following potential issues:

  in `v1.29+` versions of the baseline and restricted policies. ([#118846](https://github.com/kubernetes/kubernetes/pull/118846), [@cyclinder](https://github.com/cyclinder))
- `kubelet` now emits a metric for end-to-end pod startup latency, including image pull. ([#121041](https://github.com/kubernetes/kubernetes/pull/121041), [@ruiwen-zhao](https://github.com/ruiwen-zhao))

    - [Node Binaries](#node-binaries-26)
  - [Changelog since v1.17.0](#changelog-since-v1170-1)
    - [Action Required](#action-required)
    - [Other notable changes](#other-notable-changes-1)

<!-- END MUNGE: GENERATED_TOC -->

# v1.18.20


## Downloads for v1.18.20

### Source Code

filename | sha512 hash
-------- | -----------

* kube-apiserver now drops unneeded path information if an older version of Windows kubectl sends it. ([#44421](https://github.com/kubernetes/kubernetes/pull/44421), [@mml](https://github.com/mml))

 - End-to-end testing has been migrated from Ginkgo v1 to v2.

### SIG Multicluster

and a suite of tests to validate that the CRI server implementation meets all the requirements. This allows the CRI runtime developers to verify that their runtime conforms to CRI, without needing to set up Kubernetes components or run Kubernetes end-to-end tests. ([docs](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/cri-validation.md) and [release notes](https://github.com/kubernetes-incubator/cri-tools/releases/tag/v0.1)) ([kubernetes/features#292](https://githu...

    - [Node Binaries](#node-binaries-24)
  - [Changelog since v1.16.0](#changelog-since-v1160)
    - [Action Required](#action-required-4)
    - [Other notable changes](#other-notable-changes-8)

<!-- END MUNGE: GENERATED_TOC -->

# v1.17.17


## Downloads for v1.17.17

### Source Code

filename | sha512 hash
-------- | -----------