Containerd is downloaded and installed as the container runtime for Kubernetes. This package provides the required container management functionality.
wget https://github.com/containerd/containerd/releases/download/v1.6.16/containerd-1.6.16-linux-amd64.tar.gz -P /tmp/tar Cxzvf /usr/local /tmp/containerd-1.6.16-linux-amd64.tar.gz
The containerd systemd service is downloaded and enabled. This ensures that containerd starts automatically on boot.
runc is installed as the container runtime for containerd. It is responsible for running the containers.
This step downloads and installs the required CNI plugins, which are necessary for networking between containers in the Kubernetes cluster.
This command generates the default containerd configuration file at /etc/containerd/config.toml, which can be customized as needed.
manually edit and change
Perfect now that containerd is installed, we can move to the fun part :)
This command switches the current user to root, providing administrative privileges to run system-level commands. It is essential for performing installation and configuration tasks on the system.
These commands are used to update the package lists for the apt package manager (apt update) and then upgrade all installed packages to their latest versions (apt upgrade). This ensures that the system is up to date before installing new software.
This step changes the hostname of the system to master. The hostname identifies the machine on the network. It is important to set it properly to distinguish the Kubernetes master node. The hostnamectl command provides an easy way to manage the hostname.
This step changes the hostname of the system to master. The hostname identifies the machine on the network. It is important to set it properly to distinguish the Kubernetes master node. The hostnamectl command provides an easy way to manage the hostname.
Disabling swap is essential for Kubernetes as it can interfere with pod scheduling and memory management. The swapoff -a command disables swap immediately, and free -m displays memory usage to verify the change.
In addition to disabling swap temporarily, this step involves editing the /etc/fstab file to prevent swap from being enabled after a reboot. The lsblk command helps to verify that no swap partition exists.
This step enables the necessary kernel modules for Kubernetes networking. The overlay module is required for pod networking, and br_netfilter is needed for network filtering in the bridge.
This configures the system’s networking settings for Kubernetes. The parameters set up IP forwarding and enable network filtering for IPv4 and IPv6. The sysctl --system command applies the settings immediately.
This command installs the required tools for managing HTTPS connections, including curl for downloading files and gpg for handling public keys.
This command retrieves and adds the Google Kubernetes public key to your system, allowing it to verify packages from Kubernetes repositories.
This adds the Kubernetes package repository to your system’s APT configuration, enabling it to download Kubernetes components like kubelet, kubeadm, and kubectl.
The apt-get update command refreshes the package list with the newly added Kubernetes repository, and apt-get install installs the core Kubernetes tools: kubelet, kubeadm, and kubectl.
This step ensures that the Kubernetes packages do not get updated automatically during system package upgrades.
Flannel is a popular network fabric for Kubernetes, providing an easy way to manage networking between pods across different nodes. Here’s how you can install and configure Flannel in your Kubernetes cluster:
This command downloads and applies the Flannel network configuration to your Kubernetes cluster. The kube-flannel.yml file defines the necessary Kubernetes resources (like DaemonSets, ConfigMaps, etc.) to deploy Flannel as the network plugin. This will enable networking between pods and allow communication across the nodes in your Kubernetes cluster.
Congratulations! You have successfully installed and configured Kubernetes with containerd as the container runtime and Flannel as the network plugin. Your Kubernetes cluster is now set up and ready to manage containerized applications