[BUG] [v2.0] Failed to initialize Kubernetes cluster: CRI v1 runtime API is not implemented

[przemyslavic]

Describe the bug
There is an issue with Kubernetes cluster initialization which fails with the following error:

[ERROR CRI]: container runtime is not running
validate service connection: CRI v1 runtime API is not implemented for endpoint \\\"unix:///run/containerd/containerd.sock\\\"
rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService\

How to reproduce
Steps to reproduce the behavior:

1. execute epicli apply with k8s component enabled

Expected behavior
The cluster should be deployed without any issues

Config files

Environment

• Cloud provider: [Azure, AWS, on-prem]
• OS: [Ubuntu 20, RHEL 8.4, AlmaLinux 8.4]

epicli version: [v2.0.x]

Additional context
This seems to be related to the removal of the CRI v1alpha2 API and containerd 1.5 support in k8s v1.26 (link).
Kubeadm v1.22.4 package depends on: kubelet (>= 1.19.0), kubectl (>= 1.19.0), kubernetes-cni (>= 0.8.7) and cri-tools (>= 1.19.0).
In the installation tasks, we do not use the fixed version of cri-tools package, which means that the latest one is installed as a dependency, in this case 1.26.0, what causes the issues. Using the fixed version v1.25 of cri-tools should solve the problem.

---

DoD checklist

• Changelog
  • updated
  • not needed
• COMPONENTS.md
  • updated
  • not needed
• Schema
  • updated
  • not needed
• Backport tasks
  • created
  • not needed
• Documentation
  • added
  • updated
  • not needed
• Feature has automated tests
• Automated tests passed (QA pipelines)
  • apply
  • upgrade
  • backup/restore
• Idempotency tested
• All conversations in PR resolved