Home > Workload Solutions > Container Platforms > SUSE Containers as a Service > Guides > Certified Solution of SUSE Rancher, K3s, and SUSE Linux Enterprise Micro Using Dell PowerEdge Servers > SUSE Rancher
For the SUSE Rancher software installation, start with the installation of an enterprise-grade Linux operating system such as SUSE Linux Enterprise Micro as the base software layer.
To meet the solution stack requirements, verify that the SUSE Linux Enterprise Micro operating system is installed and configured for the node to use:
Note: When installing the node, you can point it to the respective update service. This can also be accomplished after the installation is complete using the SUSEConnect command-line tool.
While logged into the node, as root or with some privileges, perform the following steps to install SUSE Rancher:
CERT_MANAGER_VERSION=""
Note: The currently supported version of cert-manager is v1.0.4.
cat <<EOF> cert-manager-helm-crd.yaml
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
name: cert-manager
namespace: kube-system
spec:
chart: cert-manager
targetNamespace: cert-manager
version: ${CERT_MANAGER_VERSION}
repo: https://charts.jetstack.io
EOF
kubectl create namespace cert-manager
kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/${CERT_MANAGER_VERSION}/cert-manager.crds.yaml
sudo mv cert-manager-helm-crd.yaml /var/lib/rancher/k3s/server/manifests/
Monitor the progress of the installation: watch -c "kubectl get
deployments -A"
HOSTNAME=""
Note: This hostname should be resolvable to an IP address of the K3s host or a load balancer/proxy server that supports this installation of SUSE Rancher.
cat <<EOF> suse-rancher-helm-crd.yaml
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
name: rancher
namespace: kube-system
spec:
chart: rancher
targetNamespace: cattle-system
repo: https://releases.rancher.com/server-charts/stable
set:
hostname: ${HOSTNAME}
EOF
kubectl create namespace cattle-system
sudo mv suse-rancher-helm-crd.yaml /var/lib/rancher/k3s/server/manifests/
The deployment is complete all the pods have a status of Completed or Running with the number of READY pods being 1/1, 2/2, and so on.
As an option, you can create an SSH tunnel to access SUSE Rancher.
Note: This optional step is useful in cases where NAT routers or firewalls prevent the client web browser from reaching the exposed SUSE Rancher server IP address, port, or both. This step requires that a Linux host is accessible through SSH from the client system and that the Linux host can reach the exposed SUSE Rancher service. The SUSE Rancher hostname should be resolvable to the appropriate IP address by the local workstation.
To an SSH tunnel through the Linux host to the IP address of the SUSE Rancher server on the NodePort:
ssh -N -D 8080 user@Linux-host
CAUTION: This configuration routes all traffic from the web browser through the remote Linux host. When you are finished, ensure that you close the tunnel and restore the previous SOCKS Host settings.
CAUTION: On the second configuration page, verify that the Rancher Server URL is set to the hostname specified when creating the SUSE Rancher Helm Chart custom resource, and that the port is set to 443. For example, suse-rancher.sandbox.local:443.
To further optimize deployment factors, leverage the following practices:
After the successful deployment of the SUSE Rancher solution, review the SUSE Rancher product documentation for information about how downstream Kubernetes clusters can be deployed, imported, managed, and accessed.