runtime network not ready: NetworkReady=false Kubernetes after installing flannel

Question

I have existing control plane node, here is details about it:

System Info:
  Machine ID:                 b17c3aeb591145c3a2179bf59a6fd463
  System UUID:                b17c3aeb-5911-45c3-a217-9bf59a6fd463
  Boot ID:                    0aa4608e-cdd2-4501-b9c8-4bba6cc350a1
  Kernel Version:             5.11.12-1.el7.elrepo.x86_64
  OS Image:                   CentOS Linux 7 (Core)
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  docker://20.10.12
  Kubelet Version:            v1.20.14
  Kube-Proxy Version:         v1.20.14
PodCIDR:                      10.244.0.0/24
PodCIDRs:                     10.244.0.0/24
Non-terminated Pods:          (25 in total)

While, my worked node that I tri to deploy looks like this:

System Info:
  Machine ID:                 944275a550a54347ca51e69f639945ee
  System UUID:                7438EA43-DDB0-4417-A056-1552B3DD3A04
  Boot ID:                    9af4132a-f7c5-4c9c-bc5a-d38a6577ae5f
  Kernel Version:             3.10.0-1160.45.1.el7.x86_64
  OS Image:                   CentOS Linux 7 (Core)
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  docker://20.10.12
  Kubelet Version:            v1.20.14
  Kube-Proxy Version:         v1.20.14
PodCIDR:                      10.244.4.0/24
PodCIDRs:                     10.244.4.0/24
Non-terminated Pods:          (3 in total)

Having this problem:

runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized

And here is my list of commands that I used to install and join this worker node

   8. yum install kubelet-1.20.14 kubeadm-1.20.14 kubectl-1.20.14
   9. sudo setenforce 0
      sudo sed -i 's/^SELINUX=.*/SELINUX=permissive/g' /etc/selinux/config
   10 sudo sed -i '/ swap / s/^\(.*\)$/#\1/g' /etc/fstab
      sudo swapoff -a
   11 sudo modprobe overlay
      sudo modprobe br_netfilter
   12 sudo tee /etc/sysctl.d/kubernetes.conf<<EOF
      net.bridge.bridge-nf-call-ip6tables = 1
      net.bridge.bridge-nf-call-iptables = 1
      net.ipv4.ip_forward = 1
      EOF
   13 sudo sysctl --system
   14 sudo yum install -y yum-utils device-mapper-persistent-data lvm2
   15 sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo
   16 sudo yum install docker-ce-20.10.12 docker-ce-cli-20.10.12 containerd.io
   17 sudo mkdir -p /etc/systemd/system/docker.service.d
   18 sudo mkdir /etc/docker
   19 #Creating daemon json config file
   18  sudo systemctl daemon-reload
   19  sudo systemctl restart docker
   20  sudo systemctl enable docker
   21  sudo systemctl disable --now firewalld
   22  lsmod | grep br_netfilter
   23  sudo systemctl enable kubelet
   25  kubeadm join...

Also, worth to mentioned that I tried to use both Flannel and Calico

kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/2140ac876ef134e0ed5af15c65e414cf26827915/Documentation/kube-flannel.yml

#OR

kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/2140ac876ef134e0ed5af15c65e414cf26827915/Documentation/kube-flannel.yml

But error still persist

All code that I mentioned above I used to set up my new worker node