Posts

Showing posts from August, 2025

Container Runtime Interface

Install CRI-O ( Container Runtime)   CRI-O is an implementation of the Kubernetes CRI (Container Runtime Interface) to enable using OCI (Open Container Initiative) compatible runtimes. runc: runc is a low-level container runtime that directly interacts with the Linux kernel to create and run containers. runc provides the basic functionality for creating and running containers, while containerd provides a more complete environment for managing and orchestrating container workloads. ctr is unsupported debug and administrative client for interacting with the containerd daemon. Because it is unsupported, the commands,options, and operations are not guaranteed to be backward compatible or stable from release to release of the containerd project. Linux OS -> runc -> CRI https://github.com/cri-o/cri-o/releases https://github.com/opencontainers/runtime-tools https://github.com/kubernetes-sigs/cri-tools/releases # dnf install container-selinux cri-o cri-tools # systemctl enable --now ...

Venilla Kubernetes Cluster

Set Proper Hostnames # vi /etc/hosts <IP>    master <IP>    worker   Disable swap space # swapoff -a Update in fstab   Disable SELinux # vi /etc/selinux/config SELINUX=disabled     Installing traffic control (tc) for the container # dnf install -y iproute-tc   FW Rules between master and worker nodes Master Node # firewall-cmd --permanent --add-port=6443/tcp # firewall-cmd --permanent --add-port=2379-2380/tcp # firewall-cmd --permanent --add-port=10250/tcp # firewall-cmd --permanent --add-port=10251/tcp # firewall-cmd --permanent --add-port=10252/tcp # firewall-cmd --reload   Worker Nodes # firewall-cmd --permanent --add-port=10250/tcp # firewall-cmd --permanent --add-port=30000-32767/tcp                                      ...