whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update links to Dockershim Removal FAQ

Browse Source 
- Identify selected links to the Dockershim Deprecation FAQ
- Replace them with links to the updated FAQ
This commit is contained in:
Tim Bannister
2022-02-17 17:41:16 +00:00
parent b72092e0bc
commit 362da74120
3 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/reference/node/topics-on-dockershim-and-cri-compatible-runtimes.md
+1 -1
View File
@@ -12,7 +12,7 @@ with that removal.
## Kubernetes project
* Kubernetes blog: [Dockershim Deprecation FAQ](/blog/2020/12/02/dockershim-faq/) (originally published 2020/12/02)
* Kubernetes blog: [Dockershim Removal FAQ](/blog/2022/02/17/dockershim-faq/) (originally published 2022/02/17)
* Kubernetes blog: [Kubernetes is Moving on From Dockershim: Commitments and Next Steps](/blog/2022/01/07/kubernetes-is-moving-on-from-dockershim/) (published 2022/01/07)
content/en/docs/tasks/administer-cluster/migrating-from-dockershim/_index.md
+2 -1
View File
@@ -11,7 +11,8 @@ dockershim to other container runtimes.
Since the announcement of [dockershim deprecation](/blog/2020/12/08/kubernetes-1-20-release-announcement/#dockershim-deprecation)
in Kubernetes 1.20, there were questions on how this will affect various workloads and Kubernetes
installations. You can find this blog post useful to understand the problem better: [Dockershim Deprecation FAQ](/blog/2020/12/02/dockershim-faq/)
installations. Our [Dockershim Removal FAQ](/blog/2022/02/17/dockershim-faq/) is there to help you
to understand the problem better.
It is recommended to migrate from dockershim to alternative container runtimes.
Check out [container runtimes](/docs/setup/production-environment/container-runtimes/)