From 5b27a99c6c488fe49c96e3afd4d459b596a3372d Mon Sep 17 00:00:00 2001 From: Aresforchina <57612605+Aresforchina@users.noreply.github.com> Date: Fri, 6 Dec 2019 19:26:50 +0800 Subject: [PATCH] fixup 404 urls (#17954) --- .../2018-05-24-kubernetes-containerd-integration-goes-ga.md | 2 +- content/en/docs/tasks/job/parallel-processing-expansion.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/blog/_posts/2018-05-24-kubernetes-containerd-integration-goes-ga.md b/content/en/blog/_posts/2018-05-24-kubernetes-containerd-integration-goes-ga.md index 115fbef6a50..f4d79584e90 100644 --- a/content/en/blog/_posts/2018-05-24-kubernetes-containerd-integration-goes-ga.md +++ b/content/en/blog/_posts/2018-05-24-kubernetes-containerd-integration-goes-ga.md @@ -92,7 +92,7 @@ Since containerd is being used by both Kubelet and Docker Engine, this means use A containerd [namespace](https://github.com/containerd/containerd/blob/master/docs/namespaces.md) mechanism is employed to guarantee that Kubelet and Docker Engine won't see or have access to containers and images created by each other. This makes sure they won't interfere with each other. This also means that: * Users won't see Kubernetes created containers with the _docker ps_ command. Please use _crictl ps_ instead. And vice versa, users won't see Docker CLI created containers in Kubernetes or with _crictl ps_ command. The _crictl create_ and _crictl runp_ commands are only for troubleshooting. Manually starting pod or container with _crictl_ on production nodes is not recommended. -* Users won't see Kubernetes pulled images with the _docker images_ command. Please use the _crictl images_ command instead. And vice versa, Kubernetes won't see images created by _docker pull_, _docker load_ or _docker build_ commands. Please use the _crictl pull_ command instead, and _[ctr](https://github.com/containerd/containerd/blob/master/docs/man/ctr.1.md) cri load_ if you have to load an image. +* Users won't see Kubernetes pulled images with the _docker images_ command. Please use the _crictl images_ command instead. And vice versa, Kubernetes won't see images created by _docker pull_, _docker load_ or _docker build_ commands. Please use the _crictl pull_ command instead, and _[ctr](https://github.com/containerd/containerd/blob/release/1.2/docs/man/ctr.1.md) cri load_ if you have to load an image. # Summary * Containerd 1.1 natively supports CRI. It can be used directly by Kubernetes. diff --git a/content/en/docs/tasks/job/parallel-processing-expansion.md b/content/en/docs/tasks/job/parallel-processing-expansion.md index 51dbf6bbdb9..331d42f2e85 100644 --- a/content/en/docs/tasks/job/parallel-processing-expansion.md +++ b/content/en/docs/tasks/job/parallel-processing-expansion.md @@ -150,7 +150,7 @@ First, copy and paste the following template of a Job object, into a file called ```liquid -{%- set params = [{ "name": "apple", "url": "http://www.orangepippin.com/apples", }, +{%- set params = [{ "name": "apple", "url": "https://www.orangepippin.com/varieties/apples", }, { "name": "banana", "url": "https://en.wikipedia.org/wiki/Banana", }, { "name": "raspberry", "url": "https://www.raspberrypi.org/" }] %}