Create Kubernetes Cluster

Create Cluster

NOTE - This step should be completed from the Kubespray host only

With inventory in place we are ready to build the Kubernetes cluster via Ansible.

NOTE - the cluster creation may take several minutes to complete

• If the Kubespray process fails or is interpreted, run the Ansible playbook again and it will complete any incomplete steps on the subsequent run

cd ~/kubespray

source venv/bin/activate

ansible-playbook -i inventory/nexqloud/hosts.yaml -b -v --private-key=~/.ssh/id_rsa cluster.yml

GPU Node Label (Kubernetes)

Each node that provides GPUs must be labeled correctly.

NOTE - these configurations should be completed on a Kubernetes control plane node

Label Template

• Use this label template in the kubectl label command in the subsequent Label Appliction sub-section below

NOTE - please do not assign any value other than true to these labels. Setting the value to false may have unexpected consequences on the Nexqloud provider. If GPU resources are removed from a node, simply remove the Kubernetes label completely from that node.

nexqloud.network/capabilities.gpu.vendor.<vendor name>.model.<model name>=true

Label Application

Template

NOTE - if you are unsure of the <node-name> to be used in this command - issue kubectl get nodes from one of your Kubernetes control plane nodes to obtain via the NAME column of this command output

kubectl label node <node-name> <label>

Example

NOTE - issue this command/label application for all nodes hosting GPU resources

kubectl label node node1 nexqloud.network/capabilities.gpu.vendor.nvidia.model.a4000=true

Expected Output using Example

###Apply labels
root@node1:~/provider# kubectl label node node1 nexqloud.network/capabilities.gpu.vendor.nvidia.model.a4000=true
node/node1 labeled

###Verification of applied labels
root@node1:~/provider# kubectl describe node node1 | grep -A10 Labels
Labels:             nexqloud.network/capabilities.gpu.vendor.nvidia.model.a4000=true
...
...

Additional Kubernetes Configurations

NOTE - these configurations should be completed on a Kubernetes control plane node

kubectl create ns nexqloud-services
kubectl label ns nexqloud-services nexqloud.network/name=nexqloud-services nexqloud.network=true

kubectl create ns lease
kubectl label ns lease nexqloud.network=true