Add the Analytics node to the Kubernetes cluster

All operations will be executed on VM1, unless an alternative is explicitly designated.

To install the Analytics node, follow these steps:

On VM2, clone repository:

Replace {TAG_NAME} with one of available tags (to list all available tags, use git tag):

CODE

git clone https://github.com/aipix-dev/aipix-deploy.git
cd ./aipix-deploy
git checkout {TAG_NAME}
cd kubernetes/k8s-onprem/

Install the Kubernetes base components:

CODE

./install_kube_base.sh

On VM1, get a registration token and URL:

CODE

kubeadm token create --print-join-command

CODE

###Example:
sudo kubeadm join 192.168.205.164:6443 --token 3yeqrm.abnp3yof8vivcbge --discovery-token-ca-cert-hash sha256:b58cfd679a3bb49f444dfe4869fad5e19f4fba87f1d6ae5f20da06c60f51684e

Copy your token and apply it with sudo on VM2:

CODE

###Example:
sudo kubeadm join 192.168.205.164:6443 --token 3yeqrm.abnp3yof8vivcbge --discovery-token-ca-cert-hash sha256:b58cfd679a3bb49f444dfe4869fad5e19f4fba87f1d6ae5f20da06c60f51684e

On VM1, check if new node is added with the Ready status:

CODE

kubectl get nodes

CODE

###Example output:
NAME                   STATUS   ROLES           AGE     VERSION
k8s-single             Ready    control-plane   9d      v1.28.2
k8s-single-analytics   Ready    <none>          3m28s   v1.28.2

Label and taint the new node to be used only by Analytics (replace the nodek8s-single-analytics name with your node name):

CODE

##Example:
kubectl taint nodes k8s-single-analytics analytics:NoSchedule
kubectl label nodes k8s-single-analytics analytics=true