From 7947cff95a5ad66c5f2742c107212a3d777f7814 Mon Sep 17 00:00:00 2001 From: bl-ue <54780737+bl-ue@users.noreply.github.com> Date: Mon, 7 Dec 2020 10:35:48 -0500 Subject: [PATCH 1/3] Update 2020-12-02-dockershim-faq.md Fix grammar --- content/en/blog/_posts/2020-12-02-dockershim-faq.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/blog/_posts/2020-12-02-dockershim-faq.md b/content/en/blog/_posts/2020-12-02-dockershim-faq.md index eddadddb78..5d2aaa80f3 100644 --- a/content/en/blog/_posts/2020-12-02-dockershim-faq.md +++ b/content/en/blog/_posts/2020-12-02-dockershim-faq.md @@ -55,7 +55,7 @@ All your existing images will still work exactly the same. ### What about private images? -Also yes. All CRI runtimes support the same pull secrets configuration used in +Yes. All CRI runtimes support the same pull secrets configuration used in Kubernetes, either via the PodSpec or ServiceAccount. @@ -82,7 +82,7 @@ usability of other container runtimes. As an example, OpenShift 4.x has been using the [CRI-O] runtime in production since June 2019. For other examples and references you can look at the adopters of containerd and -cri-o, two container runtimes under the Cloud Native Computing Foundation ([CNCF]). +CRI-O, two container runtimes under the Cloud Native Computing Foundation ([CNCF]). - [containerd](https://github.com/containerd/containerd/blob/master/ADOPTERS.md) - [CRI-O](https://github.com/cri-o/cri-o/blob/master/ADOPTERS.md) @@ -110,7 +110,7 @@ provide an end-to-end standard for managing containers. That’s a complex question and it depends on a lot of factors. If Docker is working for you, moving to containerd should be a relatively easy swap and -has have strictly better performance and less overhead. However we encourage you +will have strictly better performance and less overhead. However, we encourage you to explore all the options from the [CNCF landscape] in case another would be an even better fit for your environment. @@ -129,7 +129,7 @@ common things to consider when migrating are: - Kubectl plugins that require docker CLI or the control socket - Kubernetes tools that require direct access to Docker (e.g. kube-imagepuller) - Configuration of functionality like `registry-mirrors` and insecure registries -- Other support scripts or daemons that expect docker to be available and are run +- Other support scripts or daemons that expect Docker to be available and are run outside of Kubernetes (e.g. monitoring or security agents) - GPUs or special hardware and how they integrate with your runtime and Kubernetes From 73adc5b617e0b597494cd1cca9dedbc99da0c78d Mon Sep 17 00:00:00 2001 From: bl-ue <54780737+bl-ue@users.noreply.github.com> Date: Mon, 7 Dec 2020 10:53:58 -0500 Subject: [PATCH 2/3] Update 2020-12-02-dont-panic-kubernetes-and-docker.md Fix grammar --- ...-12-02-dont-panic-kubernetes-and-docker.md | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/content/en/blog/_posts/2020-12-02-dont-panic-kubernetes-and-docker.md b/content/en/blog/_posts/2020-12-02-dont-panic-kubernetes-and-docker.md index e6df8971a6..b1f5113efb 100644 --- a/content/en/blog/_posts/2020-12-02-dont-panic-kubernetes-and-docker.md +++ b/content/en/blog/_posts/2020-12-02-dont-panic-kubernetes-and-docker.md @@ -13,8 +13,8 @@ as a container runtime after v1.20. **You do not need to panic. It’s not as dramatic as it sounds.** -tl;dr Docker as an underlying runtime is being deprecated in favor of runtimes -that use the [Container Runtime Interface(CRI)](https://kubernetes.io/blog/2016/12/container-runtime-interface-cri-in-kubernetes/) +TL;DR Docker as an underlying runtime is being deprecated in favor of runtimes +that use the [Container Runtime Interface (CRI)](https://kubernetes.io/blog/2016/12/container-runtime-interface-cri-in-kubernetes/) created for Kubernetes. Docker-produced images will continue to work in your cluster with all runtimes, as they always have. @@ -48,7 +48,7 @@ is a popular choice for that runtime (other common options include containerd and CRI-O), but Docker was not designed to be embedded inside Kubernetes, and that causes a problem. -You see, the thing we call “Docker” isn’t actually one thing -- it’s an entire +You see, the thing we call “Docker” isn’t actually one thing—it’s an entire tech stack, and one part of it is a thing called “containerd,” which is a high-level container runtime by itself. Docker is cool and useful because it has a lot of UX enhancements that make it really easy for humans to interact with @@ -66,11 +66,11 @@ does Kubernetes need the Dockershim? Docker isn’t compliant with CRI, the [Container Runtime Interface](https://kubernetes.io/blog/2016/12/container-runtime-interface-cri-in-kubernetes/). If it were, we wouldn’t need the shim, and this wouldn’t be a thing. But it’s -not the end of the world, and you don’t need to panic -- you just need to change +not the end of the world, and you don’t need to panic—you just need to change your container runtime from Docker to another supported container runtime. One thing to note: If you are relying on the underlying docker socket -(/var/run/docker.sock) as part of a workflow within your cluster today, moving +(`/var/run/docker.sock`) as part of a workflow within your cluster today, moving to a different runtime will break your ability to use it. This pattern is often called Docker in Docker. There are lots of options out there for this specific use case including things like @@ -82,10 +82,10 @@ use case including things like This change addresses a different environment than most folks use to interact with Docker. The Docker installation you’re using in development is unrelated to -the Docker runtime inside your Kubernetes cluster. It’s confusing, I know. As a -developer, Docker is still useful to you in all the ways it was before this +the Docker runtime inside your Kubernetes cluster. It’s confusing, we understand. +As a developer, Docker is still useful to you in all the ways it was before this change was announced. The image that Docker produces isn’t really a -Docker-specific image -- it’s an OCI ([Open Container Initiative](https://opencontainers.org/)) image. +Docker-specific image—it’s an OCI ([Open Container Initiative](https://opencontainers.org/)) image. Any OCI-compliant image, regardless of the tool you use to build it, will look the same to Kubernetes. Both [containerd](https://containerd.io/) and [CRI-O](https://cri-o.io/) know how to pull those images and run them. This is @@ -95,10 +95,10 @@ So, this change is coming. It’s going to cause issues for some, but it isn’t catastrophic, and generally it’s a good thing. Depending on how you interact with Kubernetes, this could mean nothing to you, or it could mean a bit of work. In the long run, it’s going to make things easier. If this is still confusing -for you, that’s okay -- there’s a lot going on here, Kubernetes has a lot of +for you, that’s okay—there’s a lot going on here; Kubernetes has a lot of moving parts, and nobody is an expert in 100% of it. We encourage any and all questions regardless of experience level or complexity! Our goal is to make sure -everyone is educated as much as possible on the upcoming changes. `<3` We hope +everyone is educated as much as possible on the upcoming changes. We hope this has answered most of your questions and soothed some anxieties! Looking for more answers? Check out our accompanying [Dockershim Deprecation FAQ](/blog/2020/12/02/dockershim-faq/). From 56840df61dbe685ffa2588215dc327eb982cfbee Mon Sep 17 00:00:00 2001 From: bl-ue <54780737+bl-ue@users.noreply.github.com> Date: Tue, 22 Dec 2020 11:06:47 -0500 Subject: [PATCH 3/3] Update 2020-12-02-dont-panic-kubernetes-and-docker.md --- .../blog/_posts/2020-12-02-dont-panic-kubernetes-and-docker.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2020-12-02-dont-panic-kubernetes-and-docker.md b/content/en/blog/_posts/2020-12-02-dont-panic-kubernetes-and-docker.md index b1f5113efb..944704967b 100644 --- a/content/en/blog/_posts/2020-12-02-dont-panic-kubernetes-and-docker.md +++ b/content/en/blog/_posts/2020-12-02-dont-panic-kubernetes-and-docker.md @@ -99,6 +99,6 @@ for you, that’s okay—there’s a lot going on here; Kubernetes has a lot moving parts, and nobody is an expert in 100% of it. We encourage any and all questions regardless of experience level or complexity! Our goal is to make sure everyone is educated as much as possible on the upcoming changes. We hope -this has answered most of your questions and soothed some anxieties! +this has answered most of your questions and soothed some anxieties! ❤️ Looking for more answers? Check out our accompanying [Dockershim Deprecation FAQ](/blog/2020/12/02/dockershim-faq/).