Home > Workload Solutions > Container Platforms > SUSE Containers as a Service > White Papers > Rancher Prime and RKE2 Kubernetes Cluster in APEX Private Cloud with PowerProtect Data Manager > Installing the Rancher Prime server on a Kubernetes cluster
Rancher Prime recommends installing the Rancher server on a Kubernetes cluster. In this white paper, we describe how we create a three-node Kubernetes cluster on the Linux workstation VM and then use the Helm package manager for Kubernetes to install the Rancher server. For high availability, a three-node Kubernetes cluster is recommended. Ensure that you know the networking ports needed for the Kubernetes cluster to work. For more information, see Port Requirements in the Rancher documentation.
Install Rancher server as follows:
$ curl https://raw.githubusercontent.com/helm/helm/master/scripts/get-helm-3 | bash
$ helm repo add rancher-stable https://releases.rancher.com/server-charts/stable
$ kubectl create namespace cattle-system
$ kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/v1.11.0/cert-manager.crds.yaml
In this case, we are using v1.11.0, but the newer version will work as well.
$ kubectl create namespace cert-manager
$ helm repo add jetstack https://charts.jetstack.io
$ helm repo update
$ helm install \
cert-manager jetstack/cert-manager \
--namespace cert-manager \
--version v1.8.2
$ kubectl get pods --namespace cert-manager
$ helm install rancher rancher-latest/rancher \
--namespace cattle-system \
--set hostname=rancher.apex.dell.com
$ kubectl -n cattle-system rollout status deploy/rancher
deployment "rancher" successfully rolled out
Note: Use the following workaround if the cattle-cluster-agent does not start and you receive ERROR: https://rancher.apex.dell.com/ping is not accessible (Failed to connect to rancher.apex.dell.com port 443: Connection refused):
$ kubectl edit deployment cattle-cluster-agent -n cattle-system
#Find dnsPolicy: ClusterFirst
#Change it to dnsPolicy: Default