k8s:distributions:rke2
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| k8s:distributions:rke2 [2023/10/24 13:36] – admin | k8s:distributions:rke2 [2023/11/11 18:21] (current) – admin | ||
|---|---|---|---|
| Line 56: | Line 56: | ||
| protect-kernel-defaults: | protect-kernel-defaults: | ||
| ``` | ``` | ||
| + | Create a `/ | ||
| + | ```yaml | ||
| + | mirrors: | ||
| + | docker.io: | ||
| + | endpoint: | ||
| + | - " | ||
| + | ``` | ||
| + | |||
| ### Server | ### Server | ||
| Line 81: | Line 89: | ||
| For flatcar-linux we can follow the advice on the sig-storage-local-static-provisioner website: Mount formatted block storage on `/ | For flatcar-linux we can follow the advice on the sig-storage-local-static-provisioner website: Mount formatted block storage on `/ | ||
| - | 1. Create a block device for an acdh-clusterX node in vCenter. Note that the size of the block device should be a little larger than the desired even number if GiB (example: for a 20 GiB volume create a 21 GiB disk) as there is a difference in how disk size is calculated | + | * Create a block device for an acdh-clusterX node in vCenter. Note that the size of the block device should be a little larger than the desired even number if GiB (example: for a 20 GiB volume create a 21 GiB disk) as there is a difference in how disk size is calculated |
| - | 2. Format the volume on the respective flatcar node. Use ext4 or xfs depending on the needs of the service (for example elasticsearch/ | + | * Format the volume on the respective flatcar node. Use ext4 or xfs depending on the needs of the service (for example elasticsearch/ |
| ```bash | ```bash | ||
| sudo mkfs.ext4 /dev/sdd | sudo mkfs.ext4 /dev/sdd | ||
| ``` | ``` | ||
| - | 3. reserved blocks for root are not very useful in kubernetes so set them to 0 | + | * reserved blocks for root are not very useful in kubernetes so set them to 0 |
| ```bash | ```bash | ||
| sudo tune2fs -r 0 / | sudo tune2fs -r 0 / | ||
| ``` | ``` | ||
| - | 4. Get the UUID. It is part of the output of mkfs.ext4. It is also for example available using using `ls -l / | + | * Get the UUID. It is part of the output of `mkfs.ext4` above. It is also for example available using using `ls -l / |
| - | 5. Create a UUID directory in / | + | * Create a mount unit to mount the filesystem. The filename needs to match the mount point and is encoded. |
| - | 6. Create a mount unit to mount the filesystem. The filename needs to match the mount point and is encoded. | + | |
| - | ```bash | + | ```bash |
| sudo cp / | sudo cp / | ||
| sudo vi / | sudo vi / | ||
| Line 127: | Line 135: | ||
| [Here](https:// | [Here](https:// | ||
| Kubernetes major versions are also channels. The channel latest refers to the very latest releases of K8s available. | Kubernetes major versions are also channels. The channel latest refers to the very latest releases of K8s available. | ||
| + | |||
| + | ## Troubleshooting | ||
| + | |||
| + | ### Using command line tools to manually delete container images images | ||
| + | |||
| + | ```bash | ||
| + | sudo -s | ||
| + | # as root | ||
| + | export PATH=$PATH:/ | ||
| + | export CONTAINERD_ADDRESS=/ | ||
| + | ctr -n k8s.io i rm $(ctr -n k8s.io i ls -q | grep <image name to delete, regex>) | ||
| + | # or | ||
| + | export CONTAINER_RUNTIME_ENDPOINT=unix:/// | ||
| + | crictl images | ||
| + | crictl rmi <image name to delete> | ||
| + | ``` | ||
k8s/distributions/rke2.1698147366.txt.gz · Last modified: by admin