Start a sudo shell context and Execute setup-k8s-prereqs.sh script on each machine
Execute setup-k8s-master.shscript on the machine designated as Kubernetes master (not under sudo su as otherwise you’ll setup K8S .kube/config permissions for root)
After successful initialization of the Kubernetes master, follow the kubeadm join commands output by the setup script on each agent machine
Execute setup-volumes-agent.sh script on each agent machine to create volumes for local storage
Execute kubectl apply -f local-storage-provisioner.yaml against the Kubernetes cluster to create the local storage provisioner. This will create a Storage Class named “local-storage”.
NOTE: Data controller creation can take a significant amount of time depending on configuration, network speed, and the number of nodes in the cluster.
Data controller successfully deployed. {} [root@node1 arc]# kubectl get datacontroller -n arc NAME STATE onpremises Ready [root@node1 arc]# kubectl get pod -n arc | grep -v sql NAME READY STATUS RESTARTS AGE arc-bootstrapper-job-94x7m 0/1 Completed 0 14h bootstrapper-cbf5bf94d-z9l95 1/1 Running 1 14h control-f5d8t 2/2 Running 0 14h controldb-0 2/2 Running 0 14h logsdb-0 3/3 Running 0 14h logsui-896pw 3/3 Running 3 14h metricsdb-0 2/2 Running 2 14h metricsdc-2lr8t 2/2 Running 0 14h metricsdc-79h4t 2/2 Running 2 14h metricsui-zjwnr 2/2 Running 0 14h