How to Create a Vanilla Kubernetes Cluster on BareMetal

 Kubernetes (K8s) is a powerful open-source container orchestration system, and deploying it on bare metal provides high performance and direct control over hardware. This guide walks you through setting up a vanilla Kubernetes cluster on bare metal servers.

Prerequisites
  1. Hardware Requirements:
    • At least 3 machines (1 Control Plane Node and 2 Worker Nodes).
    • Minimum specifications:
      • Control Plane Node: 2 CPUs, 2 GB RAM, 20 GB disk space.
      • Worker Node: 1 CPU, 1 GB RAM, 10 GB disk space.
  2. Operating System:
    • Ubuntu 22.04 (recommended) or any other Linux distribution.
  3. Network Setup:
    • Unique hostname for each server.
    • Static IP addresses or DHCP reservations.
    • Disabled swap (required by Kubernetes).
  4. Tools:
    • SSH access to all nodes.
    • kubectl CLI tool.
    • kubeadm for Kubernetes initialization.
    • containerd or Docker as the container runtime.

Step 1: Prepare the Nodes

Update and Install Required Packages

Log into each node and execute the following commands:

sudo apt update && sudo apt upgrade -y
sudo apt install -y apt-transport-https curl

Disable Swap

sudo swapoff -a
sudo sed -i '/ swap / s/^/#/' /etc/fstab

Load Kernel Modules and Configure sysctl

sudo modprobe overlay
sudo modprobe br_netfilter

# Persist kernel settings
cat <<EOF | sudo tee /etc/modules-load.d/k8s.conf
overlay
br_netfilter
EOF


Step 2: Install Container Runtime (docker, containerd etc..)

Install Containerd 

sudo apt install -y containerd


# Configure containerd

sudo mkdir -p /etc/containerd

containerd config default | sudo tee /etc/containerd/config.toml

sudo systemctl restart containerd

sudo systemctl enable containerd

Step 3: Install Kubernetes Components

Add Kubernetes Repository

curl -s https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -

cat <<EOF | sudo tee /etc/apt/sources.list.d/kubernetes.list

deb https://apt.kubernetes.io/ kubernetes-xenial main

EOF


sudo apt update


Install kubeadm, kubelet, and kubectl

sudo apt install -y kubelet kubeadm kubectl

sudo apt-mark hold kubelet kubeadm kubectl

Step 4: Initialize the Control Plane

On the Control Plane Node, initialize the cluster:
sudo kubeadm init --pod-network-cidr=10.244.0.0/16

Configure kubectl for the Control Plane Node

mkdir -p $HOME/.kube
sudo cp /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config

Deploy a Pod Network (e.g., Flannel or Calico)

kubectl apply -f https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/kube-flannel.yml

Step 5: Join Worker Nodes to the Cluster

On the Control Plane Node, get the join command:

kubeadm token create --print-join-command

Run the output command on each Worker Node:

sudo kubeadm join <control-plane-ip>:6443 --token <token>  --discovery-token-ca-cert-hash sha256:<hash>

Step 6: Verify the Cluster

On the Control Plane Node, check the node statuses:
kubectl get node

You should see all nodes with the status Ready.

Comments

Post a Comment

Popular posts from this blog

Managine Hadoop Cluster

If you are working on Hadoop, you’ll realize there are several shell commands available to manage your Hadoop cluster.  Hadoop administration commands. 1. Name node Commands Command Description hadoop namenode -format Format HDFS filesystem from Namenode hadoop namenode -upgrade Upgrade the NameNode start-dfs.sh Start HDFS Daemons                        stop-dfs.sh Stop HDFS Daemons start-mapred.sh Start MapReduce Daemons stop-mapred.sh Stop MapReduce Daemons hadoop namenode -recover -force Recover namenode metadata after a cluster failure (may lose data) 2. fsck Commands Command Description hadoop fsck / Filesystem check on HDFS hadoop fsck / -files Display files duri...
Read more

VENOM Vulnerability

How to Patch and Protect Linux Server against the VENOM Vulnerability # CVE-2015-3456 A very serious security problem has been found in the virtual floppy drive QEMU's code used by many computer virtualization platforms including Xen, KVM, VirtualBox, and the native QEMU client. It is called VENOM vulnerability. How can I fix VENOM vulnerability and protect my Linux server against the attack? How do I verify that my server has been fixed against the VENOM vulnerability? This is tagged as high severity security bug and it was announced on 13th May 2015. The VENOM vulnerability has existed since 2004, when the virtual Floppy Disk Controller was first added to the QEMU codebase. Since the VENOM vulnerability exists in the hypervisor’s codebase, the vulnerability is agnostic of the host operating system (Linux, Windows, Mac OS, etc.). What is the VENOM security bug (CVE-2015-3456)? An out-of-bounds memory access flaw was found in the way QEMU's virtual Floppy Disk Controller (F...
Read more

Logrotation in Linux/unix

Log files are the most valuable tools available for Linux system security. The logrotate program is used to provide the administrator with an up-to-date record of events taking place on the system. The logrotate utility may also be used to back up log files, so copies may be used to establish patterns for system use. logrotate the logrotate program is a log file manager. It is used to regularly cycle (or rotate) log files by removing the oldest ones from your system and creating new log files. It may be used to rotate based on the age of the file or the file’s size, and usually runs automatically through the cron utility. The logrotate program may also be used to compress log files and to configure e-mail to users when they are rotated. Configuration File :-  Files /var/lib/logrotate.status   >> this file update  status of recent execution of  logrotation. root@puppet:~/sadeek/big# ls -l /var/lib/logrotate/status -rw-r--r-- 1 root root 2030 Feb...
Read more