Prepare k8s Cluster

    There are many ways to build a kubernetes cluster.

    Install Kuberctl

    MIRROR="files.m.daocloud.io/"
VERSION=$(curl -L -s https://${MIRROR}dl.k8s.io/release/stable.txt)
[ $(uname -m) = x86_64 ] && curl -sSLo kubectl "https://${MIRROR}dl.k8s.io/release/${VERSION}/bin/linux/amd64/kubectl"
[ $(uname -m) = aarch64 ] && curl -sSLo kubectl "https://${MIRROR}dl.k8s.io/release/${VERSION}/bin/linux/arm64/kubectl"
chmod u+x kubectl
mkdir -p ${HOME}/bin
mv -f kubectl ${HOME}/bin

    Build Cluster

    ​
    MIRROR="files.m.daocloud.io/"
VERSION=v0.20.0
[ $(uname -m) = x86_64 ] && curl -sSLo kind "https://${MIRROR}github.com/kubernetes-sigs/kind/releases/download/${VERSION}/kind-linux-amd64"
[ $(uname -m) = aarch64 ] && curl -sSLo kind "https://${MIRROR}github.com/kubernetes-sigs/kind/releases/download/${VERSION}/kind-linux-arm64"
chmod u+x kind
mkdir -p ${HOME}/bin
mv -f kind ${HOME}/bin

    Creating a Kubernetes cluster is as simple as kind create cluster

    kind create cluster --name test

    and the you can visit https://kind.sigs.k8s.io/docs/user/quick-start/ for mode detail.

    MIRROR="files.m.daocloud.io/"
[ $(uname -m) = x86_64 ] && curl -sSLo minikube "https://${MIRROR}storage.googleapis.com/minikube/releases/latest/minikube-linux-amd64"
[ $(uname -m) = aarch64 ] && curl -sSLo minikube "https://${MIRROR}storage.googleapis.com/minikube/releases/latest/minikube-linux-arm64"
chmod u+x minikube
mkdir -p ${HOME}/bin
mv -f minikube ${HOME}/bin

    [Optional] disable aegis service and reboot system for aliyun

    sudo systemctl disable aegis && sudo reboot

    after you download binary, you can start your cluster

    minikube start --kubernetes-version=v1.27.10 --image-mirror-country=cn --image-repository=registry.cn-hangzhou.aliyuncs.com/google_containers --cpus=6 --memory=24g --disk-size=100g

    add alias for convinence

    alias kubectl="minikube kubectl --"

    and then you can visit https://minikube.sigs.k8s.io/docs/start/ for more detail.

    Prerequisites

    • Hardware Requirements:

      1. At least 2 GB of RAM per machine (minimum 1 GB)
      2. 2 CPUs on the master node
      3. Full network connectivity among all machines (public or private network)

    • Operating System:

      1. Ubuntu 20.04/18.04, CentOS 7/8, or any other supported Linux distribution.

    • Network Requirements:

      1. Unique hostname, MAC address, and product_uuid for each node.
      2. Certain ports need to be open (e.g., 6443, 2379-2380, 10250, 10251, 10252, 10255, etc.)

    • Disable Swap:

      sudo swapoff -a

    Steps to Setup Kubernetes Cluster

    1. Prepare Your Servers Update the Package Index and Install Necessary Packages On all your nodes (both master and worker):
    sudo apt-get update
sudo apt-get install -y apt-transport-https ca-certificates curl

    Add the Kubernetes APT 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 http://apt.kubernetes.io/ kubernetes-xenial main
EOF

    Install kubeadm, kubelet, and kubectl

    sudo apt-get update
sudo apt-get install -y kubelet kubeadm kubectl
sudo apt-mark hold kubelet kubeadm kubectl
    1. Initialize the Master Node On the master node, initialize the Kubernetes control plane:
    sudo kubeadm init --pod-network-cidr=192.168.0.0/16

    The –pod-network-cidr flag is used to set the Pod network range. You might need to adjust this based on your network provider

    Set up Local kubeconfig

    mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config
    1. Install a Pod Network Add-on You can install a network add-on like Flannel, Calico, or Weave. For example, to install Calico:
    1. Join Worker Nodes to the Cluster On each worker node, run the kubeadm join command provided at the end of the kubeadm init output on the master node. It will look something like this:
    sudo kubeadm join <master-ip>:6443 --token <token> --discovery-token-ca-cert-hash sha256:<hash>

    If you lost the join command, you can create a new token on the master node:

    sudo kubeadm token create --print-join-command
    1. Verify the Cluster Once all nodes have joined, you can verify the cluster status from the master node:
    kubectl get nodes

    This command should list all your nodes with the status “Ready”.