3 ingress nodes (managing external access to the cluster)
7 worker nodes (2 high profile and 5 low)
Note: It is not recommended to add VMs to the cluster yourself. If you need more power please log a ticket in the common gitlab and we will manage the scale-up (or down) for you.
The cluster is split in namespaces. Any pods of a particular namespace does not know the other (but they can access services provided by other namespaces).
By default all deployments are installed in the "Default" namespace but you can create as many namespace as necessary.
Interact with the cluster
kubectl get nodes # list all the nodes of a cluster
kubectl get pods -n log # list all the pods of the namespace log
kubectl get pods -n log -o wide # list all pods in NS log and also the workers where they are running
kubectl get svc -n log # list all deployed services in the NS log
kubectl get deployments -n log # list all application deployments in the log NS
kubectl logs [pod name] -n log # display the logs of a particular pod of the NS log, use -f for following (tail)
kubectl exec -it [pod name] /bin/bash # run a shell in the pod
kubectl get ev -n log # Give the last K8S events of the log NS
Deploy new software
You can find several examples in the repository for services already deployed in your cluster.
Basically you can deploy things with: