From 2da1358f86920244daf7dddf6a3e97563cdfa147 Mon Sep 17 00:00:00 2001 From: Lantao Liu Date: Tue, 18 Sep 2018 10:27:33 -0700 Subject: [PATCH] Update v1.2.0-rc release note. Signed-off-by: Lantao Liu --- releases/v1.2.0-rc.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/releases/v1.2.0-rc.toml b/releases/v1.2.0-rc.toml index 96f4eb52f..92d3438a5 100644 --- a/releases/v1.2.0-rc.toml +++ b/releases/v1.2.0-rc.toml @@ -40,7 +40,7 @@ Containerd 1.2 is validated against Kubernetes v1.11 and v1.12, but it is also c Users can: * Configure alternative runtime handlers with the config option `plugins.cri.containerd.runtimes.runtime_handler_name`, e.g. `plugins.cri.containerd.runtimes.kata`. ([config.md](https://github.com/containerd/cri/blob/release/1.2/docs/config.md)) -* Use the alternative runtime handler in Kubernetes by creating `RuntimeClass` for the runtime handler, and specifying `RuntimeClassName` in the pod spec. ([examples](https://github.com/kubernetes/community/blob/master/keps/sig-node/0014-runtime-class.md#examples)) +* Use the alternative runtime handler in Kubernetes by creating `RuntimeClass` for the runtime handler, and specifying `RuntimeClassName` in the pod spec. ([doc](https://github.com/kubernetes/website/blob/release-1.12/content/en/docs/concepts/containers/runtime-class.md)) ***The `plugins.cri.containerd.untrusted_workload_runtime` config option and `io.kubernetes.cri.untrusted-workload` pod annotation are still functional, but start being deprecated. It is recommended to migrate to the `RuntimeClass` api.***