Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Maintenance.md #335

Merged
merged 3 commits into from
Jan 25, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 14 additions & 14 deletions documentation/Maintenance.md
Original file line number Diff line number Diff line change
Expand Up @@ -1004,6 +1004,20 @@ If there is such disk, it will be **cleared** and re-mounted to `/var/lib/contai

**Warning**: The migration procedure removes the docker daemon from all nodes in the cluster.

### Procedure Execution Steps

This procedure includes the following steps:
1. Verify and merge all the specified parameters into the inventory.
2. Install and configure containerd and podman.
3. Install crictl.
4. Implement the following steps on each control-plane and worker node by node.
1. Drain the node.
2. Update configurations on the node for migration to containerd.
3. Move the pods on the node from the docker's containers to those of containerd.
4. Uncordon the node.

**Warning**: Before starting the migration procedure, verify that you already have the actual claster.yaml structure. The services.docker scheme is deprecated.

### migrate_cri Parameters

The following sections describe the `migrate_cri` parameters.
Expand Down Expand Up @@ -1077,20 +1091,6 @@ thirdparties:
source: https://github.com/kubernetes-sigs/cri-tools/releases/download/v1.20.0/crictl-v1.20.0-linux-amd64.tar.gz
```


### Procedure Execution Steps

1. Verify and merge all the specified parameters into the inventory.
2. Install and configure containerd and podman.
3. Install crictl.
4. Implement the following steps on each control-plane and worker node by node.
1. Drain the node.
2. Update configurations on the node for migration to containerd.
3. Move the pods on the node from the docker's containers to those of containerd.
4. Uncordon the node.

**Warning**: Before starting the migration procedure, verify that you already have the actual claster.yaml structure. The services.docker scheme is deprecated.

## Admission Migration Procedure

Since Kubernetes v1.20 Pod Security Policy (PSP) has been deprecated and will be delete in Kubernetes 1.25 the migration procedure
Expand Down