Skip to content

Commit 17cc361

Browse files
Merge pull request #247835 from Nickomang/main
Added link to dockershim removal FAQ
2 parents 6773e1e + 5ff2cbf commit 17cc361

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/aks/cluster-configuration.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ A container runtime is software that executes containers and manages container i
2424

2525
With a `containerd`-based node and node pools, instead of talking to the `dockershim`, the kubelet talks directly to `containerd` using the CRI (container runtime interface) plugin, removing extra hops in the data flow when compared to the Docker CRI implementation. As such, you see better pod startup latency and less resource (CPU and memory) usage.
2626

27-
By using `containerd` for AKS nodes, pod startup latency improves and node resource consumption by the container runtime decreases. These improvements through this new architecture enable kubelet communicating directly to `containerd` through the CRI plugin. While in a Moby/docker architecture, kubelet communicates to the `dockershim` and docker engine before reaching `containerd`, therefore having extra hops in the data flow.
27+
By using `containerd` for AKS nodes, pod startup latency improves and node resource consumption by the container runtime decreases. These improvements through this new architecture enable kubelet communicating directly to `containerd` through the CRI plugin. While in a Moby/docker architecture, kubelet communicates to the `dockershim` and docker engine before reaching `containerd`, therefore having extra hops in the data flow. For more details on the origin of the `dockershim` and its deprecation, see the [Dockershim removal FAQ][kubernetes-dockershim-faq].
2828

2929
![Docker CRI 2](media/cluster-configuration/containerd-cri.png)
3030

@@ -515,6 +515,7 @@ az aks update -n aksTest -g aksTest –-nrg-lockdown-restriction-level Unrestric
515515
[azurerm-azurelinux]: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/kubernetes_cluster_node_pool#os_sku
516516
[general-usage]: https://kubernetes.io/docs/tasks/debug/debug-cluster/crictl/#general-usage
517517
[client-config-options]: https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/crictl.md#client-configuration-options
518+
[kubernetes-dockershim-faq]: https://kubernetes.io/blog/2022/02/17/dockershim-faq/#why-was-the-dockershim-removed-from-kubernetes
518519

519520
<!-- LINKS - internal -->
520521
[azure-cli-install]: /cli/azure/install-azure-cli
@@ -526,7 +527,7 @@ az aks update -n aksTest -g aksTest –-nrg-lockdown-restriction-level Unrestric
526527
[az-feature-register]: /cli/azure/feature#az_feature_register
527528
[az-feature-list]: /cli/azure/feature#az_feature_list
528529
[az-provider-register]: /cli/azure/provider#az_provider_register
529-
[aks-add-np-containerd]: /create-node-pools.md#add-a-windows-server-node-pool-with-containerd
530+
[aks-add-np-containerd]: create-node-pools.md#add-a-windows-server-node-pool-with-containerd
530531
[az-aks-create]: /cli/azure/aks#az-aks-create
531532
[az-aks-update]: /cli/azure/aks#az-aks-update
532533
[baseline-reference-architecture-aks]: /azure/architecture/reference-architectures/containers/aks/baseline-aks

0 commit comments

Comments
 (0)