Also added

/etc/default/kubelet

KUBELET_EXTRA_ARGS="--container-runtime=remote --container-runtime-endpoint=unix:///var/run/crio/crio.sock"

Hi @serewicz thanks for replying.

I'm sure I've executed all those steps. I am going to restart again completely from scratch and follow your described procedure.

The only thing different should be my hostname, and respectively, the /etc/hosts file:

olmo@te-olmo-k8m0101:~$ cat /etc/hosts
127.0.0.1       localhost
172.21.90.50    te-olmo-k8m0101.my.domain te-olmo-k8m0101 k8scp
172.21.90.51    te-olmo-k8m0102.my.domain      te-olmo-k8m0102
172.21.90.52    te-olmo-k8m0103.my.domain      te-olmo-k8m0103
172.21.90.53    te-olmo-k8w0101.my.domain      te-olmo-k8w0101
172.21.90.54    te-olmo-k8w0102.my.domain      te-olmo-k8w0102
172.21.90.55    te-olmo-hap0101.my.domain      te-olmo-hap0101

# The following lines are desirable for IPv6 capable hosts
::1     localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

which should be fine...

ftr:

olmo@te-olmo-k8m0101:~$ cat /etc/sysctl.d/99-kubernetes-cri.conf
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_forward = 1
net.bridge.bridge-nf-call-ip6tables = 1
olmo@te-olmo-k8m0101:~$ sudo sysctl -a | grep "bridge-nf-call\|ip_forward"
net.bridge.bridge-nf-call-arptables = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.bridge.bridge-nf-call-iptables = 1
net.ipv4.ip_forward = 1
net.ipv4.ip_forward_use_pmtu = 0

root@te-olmo-k8m0101:/etc/modules-load.d# cat 001-kubernetes.conf
overlay
br_netfilter
root@te-olmo-k8m0101:/root# lsmod | grep 'overlay\|br_netfilter'
br_netfilter           24576  0
bridge                155648  1 br_netfilter
overlay

olmo@te-olmo-k8m0101:~$ ping k8scp
PING te-olmo-k8m0101 (172.21.90.50) 56(84) bytes of data.
64 bytes from te-olmo-k8m0101 (172.21.90.50): icmp_seq=1 ttl=64 time=0.032 ms
64 bytes from te-olmo-k8m0101 (172.21.90.50): icmp_seq=2 ttl=64 time=0.049 ms

In regarding of not-mentioned config file I ment the crio.conf file, not the kubeadm-crio.yaml file:

s_03  ❯  ls -l
total 36
-rw-r--r-- 1 ruperto ruperto   121 Nov  2  2020 99-kubernetes-cri.conf
-rw-r--r-- 1 ruperto ruperto 10200 Aug 23 14:32 crio.conf
-rw-r--r-- 1 ruperto ruperto   958 Nov  2  2020 first.yaml
-rw-r--r-- 1 ruperto ruperto   163 Sep 20 15:36 kubeadm-config.yaml
-rw-r--r-- 1 ruperto ruperto  1699 Aug 23 14:32 kubeadm-crio.yaml
-rw-r--r-- 2 ruperto ruperto   206 Oct 23  2020 low-resource-range.yaml
-rw-r--r-- 1 ruperto ruperto  2469 Aug 23 14:32 second.yaml

however placing or not placing the file ( /etc/crio/crio.conf ) did not make a difference.

i'm going to try again and get back on this.

thanks for the reply.

however...

you are correct. and i screwed up an installation earlier.

i removed containers-common and deleted /etc/crio* /etc/containers and /etc/cni

and tried again and it worked.

still stuck with the same issue when trying to go HA

try to reinstall from scratch.

and came back to my own post however, deleting

i removed containers-common and deleted rm -rf /etc/crio* /etc/containers and /etc/cni

i fail to be able install crio....

crio is reinstall containers-common as it should however, for some reason this is not creating all files as listed in the package.

$ dpkg -L containers-common
/.
/etc
/etc/containers
/etc/containers/policy.json
/etc/containers/registries.conf
/etc/containers/registries.conf.d
/etc/containers/registries.conf.d/000-shortnames.conf
/etc/containers/registries.d
/etc/containers/registries.d/default.yaml
/etc/containers/storage.conf
..

$ find /etc/containers/
/etc/containers/
/etc/containers/registries.d
/etc/containers/registries.conf.d

and crio fails with runc error, after setting it like above
/etc/crio/crio.conf.d/10-runc.conf
10-runc.conf
[crio.runtime]
default_runtime = "runc"
[crio.runtime.runtimes]
[crio.runtime.runtimes.runc]
runtime_path="/usr/lib/cri-o-runc/sbin/runc"

it mentions the missing policy.conf

so it's getting late and will try again tomorrow.

totally unclear why containers-common is not installing all required files.

i can rebootstrap the entire box as my other prepared machines still have the correct content of /etc/containers but i wish to know what causes me to fail to just to install crio at this stage.