Repository: vscode
Issue: View Zone Alignment Bug
Labels: bug,merge-editor

```json
{
    "languageId": "markdown",
    "base": "---\ntitle: Migration Container Runtime Engine\nlang: en\npermalink: /imke/clusterlifecycle/clustermigrations/containerruntimeengine/\nnav_order: 5000\nparent: Cluster Lifecycle\nhas_children: false\n---\n\n## General Container Runtime Information\n\nFor a long time now Docker (or rather the dockershim to be more precise) has\nbeen used as the default Container Runtime Engine in the underlying\ninfrastructure of Kubernetes. But maintaining this dockershim on the\ndevelopment side has become a heaven burden on the Kubernetes maintainers.\nTo reduce this burden the CRI standard has been implemented, but unfortunately\nDocker itself does not implement this standard (hence the dockershim!).\n\nWith the Kubernetes v1.20 release the deprecation of the dockershim has been\nannounced, scheduled for the release of v1.24. So to be able to upgrade to\nKubernetes v1.24 we will need the Kubernetes nodes to run a different\ncontainer runtime engine which is CRI-standard compatible. For iMKE this\nwill be containerd.\n\n## Changing the Container Runtime Engine Config\n\nTo upgrade from docker to containerd the following steps are needed:\n\n1. edit the cluster configuration\n\n   ![edit-cluster-config](edit-cluster.png)\n\n1. change the value of the *Container Runtime* field from *docker* to *containerd* and save the changes\n\n   ![switch-cre-config](switch-cre.png)\n\n\n## Activating the Config Change\n\nFor the change to take effect you need to rotate your worker nodes once.\nThis can be done by either upgrading to a new Kubernetes version or by\ndoing a restart of the rollout of your MachineDeployment. While the prior\ncan be done in the webUI easily (and is already covered by [here](/imke/clusterlifecycle/upgradingacluster/)),\nthe latter will be shown below.\n\n1. check which container runtime your workers are currently using:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   ```\n\n   Here we see in the output that docker is still used as the container runtime.\n1. restart the MachineDeployment by\n    1. clicking on the MachineDeployment of the cluster\n\n       ![choose-machinedeployment](choose-machinedeployment.png)\n\n    1. clicking on the restart button\n\n       ![click-on-restart-button](click-on-restart-button.png)\n\n    1. confirming the restart of the MachineDeployment\n\n       ![confirm-restart](confirm-restart.png)\n\n   Now one after another a new machine will be added and an old machine will be removed after it's workload has been transferred into the rest of the cluster. After the last old machine has been removed the restart of the\n   MachineDeployment is complete.\n1. now to check again which container runtime powers your worker nodes now:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   ```\n\nThis concludes the migration of your Kubernetes clusters container runtime\nfrom *docker* to *containerd*.\n\n## Learn More\n\nMore background information on the container runtime engines for Kubernetes can be\nfound here:\n\n* <https://kubernetes.io/blog/2020/12/02/dockershim-faq/>\n* <https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/>\n",
    "input1": "---\ntitle: Migration Container Runtime Engine\nlang: en\npermalink: /gks/clusterlifecycle/clustermigrations/containerruntimeengine/\nnav_order: 4600\nparent: Cluster Lifecycle\nhas_children: false\n---\n# Migration Container Runtime Engine\n\n## General Container Runtime Information\n\nFor a long time now Docker (or rather the dockershim to be more precise) has\nbeen used as the default Container Runtime Engine in the underlying\ninfrastructure of Kubernetes. But maintaining this dockershim on the\ndevelopment side has become a heavy burden on the Kubernetes maintainers.\nTo reduce this burden the CRI standard has been implemented, but unfortunately\nDocker itself does not implement this standard (hence the dockershim!).\n\nWith the Kubernetes v1.20 release the deprecation of the dockershim has been\nannounced, scheduled for the release of v1.24. So to be able to upgrade to\nKubernetes v1.24 we will need the Kubernetes nodes to run a different\ncontainer runtime engine which is CRI-standard compatible. For GKS this\nwill be containerd.\n\n## Changing the Container Runtime Engine Config\n\nTo upgrade from Docker to containerd the following steps are needed:\n\n1. Edit the cluster configuration.\n![edit-cluster-config](../../images/MigContRun01.png)\n\n1. Change the value of the *Container Runtime* field from *docker* to *containerd* and save the changes.\n\n![switch-cre-config](../../images/MigContRun02.png)\n\n## Activating the Config Change\n\nFor the change to take effect, you need to rotate your worker nodes once.\nThis can be done by either upgrading to a new Kubernetes version or by\ndoing a restart of the rollout of your MachineDeployment. While the prior\ncan be done in the Web UI easily (and is already covered by [here](/gks/clusterlifecycle/upgradingacluster/)),\nthe latter will be shown below.\n\n1. Check which container runtime your workers are currently using:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   ```\n\n   Here we see in the output that docker is still used as the container runtime.\n1. Restart the Machine Deployment as follows:\n    1. Click on the Machine Deployment of the cluster.\n![choose-machinedeployment](../../images/MigContRun03.png)\n\n    1. Click on the Restart button.\n![click-on-restart-button](../../images/MigContRun04.png)\n\n    1. Confirm the restart of the Machine Deployment.\n\n ![confirm-restart](../../images/MigContRun05.png)\n\n   Now one after another, a new machine will be added and an old machine will be removed after its workload has been transferred into the rest of the cluster. After the last old machine has been removed, the restart of the\n   MachineDeployment is complete.\n2. Now check again, which container runtime powers your worker nodes:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   ```\n\nThis concludes the migration of your Kubernetes clusters container runtime\nfrom *docker* to *containerd*.\n\n## Learn More\n\nMore background information on the container runtime engines for Kubernetes is available here:\n\n* <https://kubernetes.io/blog/2020/12/02/dockershim-faq/>\n* <https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/>\n",
    "input2": "---\ntitle: Migration Container Runtime Engine\nlang: \"en\"\npermalink: /imke/clusterlifecycle/clustermigrations/containerruntimeengine/\nnav_order: 5000\nparent: Cluster Lifecycle\nhas_children: false\n---\n\n## General Container Runtime Information\n\nFor a long time now Docker (or rather the dockershim to be more precise) has\nbeen used as the default Container Runtime Engine in the underlying\ninfrastructure of Kubernetes. But maintaining this dockershim on the\ndevelopment side has become a heaven burden on the Kubernetes maintainers.\nTo reduce this burden the CRI standard has been implemented, but unfortunately\nDocker itself does not implement this standard (hence the dockershim!).\n\nWith the Kubernetes v1.20 release the deprecation of the dockershim has been\nannounced, scheduled for the release of v1.24. So to be able to upgrade to\nKubernetes v1.24 we will need the Kubernetes nodes to run a different\ncontainer runtime engine which is CRI-standard compatible. For iMKE this\nwill be containerd.\n\n## Changing the Container Runtime Engine Config\n\nTo upgrade from docker to containerd the following steps are needed:\n\n1. edit the cluster configuration\n\n   ![edit-cluster-config](edit-cluster.png)\n\n1. change the value of the *Container Runtime* field from *docker* to *containerd* and save the changes\n\n   ![switch-cre-config](switch-cre.png)\n\n## Activating the Config Change\n\nFor the change to take effect you need to rotate your worker nodes once.\nThis can be done by either upgrading to a new Kubernetes version or by\ndoing a restart of the rollout of your MachineDeployment. While the prior\ncan be done in the webUI easily (and is already covered by [here](/imke/clusterlifecycle/upgradingacluster/)),\nthe latter will be shown below.\n\n1. check which container runtime your workers are currently using:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   ```\n\n   Here we see in the output that docker is still used as the container runtime.\n1. restart the MachineDeployment by\n    1. clicking on the MachineDeployment of the cluster\n\n       ![choose-machinedeployment](choose-machinedeployment.png)\n\n    1. clicking on the restart button\n\n       ![click-on-restart-button](click-on-restart-button.png)\n\n    1. confirming the restart of the MachineDeployment\n\n       ![confirm-restart](confirm-restart.png)\n\n   Now one after another a new machine will be added and an old machine will be removed after it's workload has been transferred into the rest of the cluster. After the last old machine has been removed the restart of the\n   MachineDeployment is complete.\n1. now to check again which container runtime powers your worker nodes now:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   ```\n\nThis concludes the migration of your Kubernetes clusters container runtime\nfrom *docker* to *containerd*.\n\n## Learn More\n\nMore background information on the container runtime engines for Kubernetes can be\nfound here:\n\n* <https://kubernetes.io/blog/2020/12/02/dockershim-faq/>\n* <https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/>\n",
    "result": "---\ntitle: Migration Container Runtime Engine\nlang: \"en\"\npermalink: /gks/clusterlifecycle/clustermigrations/containerruntimeengine/\nnav_order: 4600\nparent: Cluster Lifecycle\nhas_children: false\n---\n# Migration Container Runtime Engine\n\n## General Container Runtime Information\n\nFor a long time now Docker (or rather the dockershim to be more precise) has\nbeen used as the default Container Runtime Engine in the underlying\ninfrastructure of Kubernetes. But maintaining this dockershim on the\ndevelopment side has become a heavy burden on the Kubernetes maintainers.\nTo reduce this burden the CRI standard has been implemented, but unfortunately\nDocker itself does not implement this standard (hence the dockershim!).\n\nWith the Kubernetes v1.20 release the deprecation of the dockershim has been\nannounced, scheduled for the release of v1.24. So to be able to upgrade to\nKubernetes v1.24 we will need the Kubernetes nodes to run a different\ncontainer runtime engine which is CRI-standard compatible. For GKS this\nwill be containerd.\n\n## Changing the Container Runtime Engine Config\n\nTo upgrade from Docker to containerd the following steps are needed:\n\n1. Edit the cluster configuration.\n![edit-cluster-config](../../images/MigContRun01.png)\n\n1. Change the value of the *Container Runtime* field from *docker* to *containerd* and save the changes.\n\n![switch-cre-config](../../images/MigContRun02.png)\n\n   ![switch-cre-config](switch-cre.png)\n\n\n## Activating the Config Change\n\nFor the change to take effect, you need to rotate your worker nodes once.\nThis can be done by either upgrading to a new Kubernetes version or by\ndoing a restart of the rollout of your MachineDeployment. While the prior\ncan be done in the Web UI easily (and is already covered by [here](/gks/clusterlifecycle/upgradingacluster/)),\nthe latter will be shown below.\n\n1. Check which container runtime your workers are currently using:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   ```\n\n   Here we see in the output that docker is still used as the container runtime.\n1. Restart the Machine Deployment as follows:\n    1. Click on the Machine Deployment of the cluster.\n![choose-machinedeployment](../../images/MigContRun03.png)\n\n    1. Click on the Restart button.\n![click-on-restart-button](../../images/MigContRun04.png)\n\n    1. Confirm the restart of the Machine Deployment.\n\n ![confirm-restart](../../images/MigContRun05.png)\n\n   Now one after another, a new machine will be added and an old machine will be removed after its workload has been transferred into the rest of the cluster. After the last old machine has been removed, the restart of the\n   MachineDeployment is complete.\n2. Now check again, which container runtime powers your worker nodes:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   ```\n\nThis concludes the migration of your Kubernetes clusters container runtime\nfrom *docker* to *containerd*.\n\n## Learn More\n\nMore background information on the container runtime engines for Kubernetes is available here:\n\n* <https://kubernetes.io/blog/2020/12/02/dockershim-faq/>\n* <https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/>\n",
    "initialResult": "---\ntitle: Migration Container Runtime Engine\n<<<<<<< HEAD:docs/_imke/clusterlifecycle/clustermigrations/containerruntimeengine/index.en.md\nlang: \"en\"\npermalink: /imke/clusterlifecycle/clustermigrations/containerruntimeengine/\nnav_order: 5000\n=======\nlang: en\npermalink: /gks/clusterlifecycle/clustermigrations/containerruntimeengine/\nnav_order: 4600\n>>>>>>> main:docs/_gks/clusterlifecycle/clustermigrations/containerruntimeengine/index.en.md\nparent: Cluster Lifecycle\nhas_children: false\n---\n# Migration Container Runtime Engine\n\n## General Container Runtime Information\n\nFor a long time now Docker (or rather the dockershim to be more precise) has\nbeen used as the default Container Runtime Engine in the underlying\ninfrastructure of Kubernetes. But maintaining this dockershim on the\ndevelopment side has become a heavy burden on the Kubernetes maintainers.\nTo reduce this burden the CRI standard has been implemented, but unfortunately\nDocker itself does not implement this standard (hence the dockershim!).\n\nWith the Kubernetes v1.20 release the deprecation of the dockershim has been\nannounced, scheduled for the release of v1.24. So to be able to upgrade to\nKubernetes v1.24 we will need the Kubernetes nodes to run a different\ncontainer runtime engine which is CRI-standard compatible. For GKS this\nwill be containerd.\n\n## Changing the Container Runtime Engine Config\n\nTo upgrade from Docker to containerd the following steps are needed:\n\n1. Edit the cluster configuration.\n![edit-cluster-config](../../images/MigContRun01.png)\n\n1. Change the value of the *Container Runtime* field from *docker* to *containerd* and save the changes.\n\n<<<<<<< HEAD:docs/_imke/clusterlifecycle/clustermigrations/containerruntimeengine/index.en.md\n=======\n![switch-cre-config](../../images/MigContRun02.png)\n\n>>>>>>> main:docs/_gks/clusterlifecycle/clustermigrations/containerruntimeengine/index.en.md\n## Activating the Config Change\n\nFor the change to take effect, you need to rotate your worker nodes once.\nThis can be done by either upgrading to a new Kubernetes version or by\ndoing a restart of the rollout of your MachineDeployment. While the prior\ncan be done in the Web UI easily (and is already covered by [here](/gks/clusterlifecycle/upgradingacluster/)),\nthe latter will be shown below.\n\n1. Check which container runtime your workers are currently using:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   Container Runtime Version:  docker://19.3.15\n   ```\n\n   Here we see in the output that docker is still used as the container runtime.\n1. Restart the Machine Deployment as follows:\n    1. Click on the Machine Deployment of the cluster.\n![choose-machinedeployment](../../images/MigContRun03.png)\n\n    1. Click on the Restart button.\n![click-on-restart-button](../../images/MigContRun04.png)\n\n    1. Confirm the restart of the Machine Deployment.\n\n ![confirm-restart](../../images/MigContRun05.png)\n\n   Now one after another, a new machine will be added and an old machine will be removed after its workload has been transferred into the rest of the cluster. After the last old machine has been removed, the restart of the\n   MachineDeployment is complete.\n2. Now check again, which container runtime powers your worker nodes:\n\n   ```bash\n   $ kubectl describe node  | grep \"Container Runtime Version\"\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   Container Runtime Version:  containerd://1.5.4\n   ```\n\nThis concludes the migration of your Kubernetes clusters container runtime\nfrom *docker* to *containerd*.\n\n## Learn More\n\nMore background information on the container runtime engines for Kubernetes is available here:\n\n* <https://kubernetes.io/blog/2020/12/02/dockershim-faq/>\n* <https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/>\n"
}
```
<img width="1514" alt="image" src="https://user-images.githubusercontent.com/2931520/195066475-a8ba92b5-d7cd-483e-ae91-aedba0ba7643.png">