Home > Communication Service Provider Solutions > Telecom Multicloud Foundation > Open Telecom Ecosystem > Guides > Certified Solution of SUSE Rancher 2.6.3, K3s 1.21.7 and SUSE Linux Enterprise Micro 5.1 on 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.
rancher/v2.6/en/installation/requirements/ports/) or
Note: This is the easiest way of installing SUSE Rancher with self-signed certificates.
#Obtain helm binary https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash
Note: Enable the respective kubeconfig setting for kubectl , K3s - /etc/rancher/k3s/k3s.yml, to be leveraged by helm command. (Example: chmod 600 /etc/rancher/k3s/k3s.yaml, export KUBECONFIG=/etc/rancher/k3s/k3s.yaml)
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.5.1.
kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/releases/download/${CERT_MANAGER_VERSION}/cert-manager.crds.yaml
# Add the Jetstack Helm repository
helm repo add jetstack https://charts.jetstack.io
# Update your local Helm chart repository cache
helm repo update
# Install the cert-manager Helm chart
helm install cert-manager jetstack/cert-manager \
--namespace cert-manager \
--create-namespace \
--version ${CERT_MANAGER_VERSION}
kubectl get pods --namespace cert-manager
watch -c "kubectl get deployments -A"
The deployment is complete all the deployments (cert-manager, cert-manager-cainjector, and cert-manager-webhook) show at least one as AVAILABLE.
helm repo add rancher-stable https://releases.rancher.com/server-charts/stable
kubectl create namespace cattle-system
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.
REPLICAS=""
RANCHER_VERSION=""
helm install rancher rancher-stable/rancher \
--namespace cattle-system \
--set hostname=${HOSTNAME} \
--set version=${RANCHER_VERSION} \
--set replicas=${REPLICAS}
kubectl -n cattle-system rollout status deploy/rancher
watch -c "kubectl get deployments -A"
kubectl get all -A
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, rancherxr11.dsp.lab: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.
Rancher simplifies the creation of K3S Kubernetes clusters by allowing you to create them through the Rancher UI rather than more complex alternatives. Rancher provides multiple options for launching a cluster. Use the option that best fits your use case.
Note: For more information, see the Setting up Kubernetes Clusters in Rancher page.
To create a downstream custom cluster using the Rancher user interface, perform the following steps:
There are 2 ways to configure the K3S cluster:
To set up the K3S server, perform the following steps:
To set up the K3S agents, perform the following steps:
All K3S servers and agents join the K3S HA cluster and display in Cluster Management after they are registered.
To set up a K3S standalone cluster, perform the following steps:
The K3S standalone cluster displays in Cluster Management after it is registered.
Rancher Continuous Delivery is powered by Fleet, which comes preinstalled with Rancher. Fleet is GitOps at scale, designed to manage up to a million clusters. and is lightweight enough that is works great for a single cluster. Fleet shows its true performance capabilities when used with many clusters, deployments, or teams in a single organization.
Fleet can manage git deployments of raw Kubernetes YAML, Helm charts, Kustomize, or any combination of the three. Regardless of the source, all resources are dynamically turned into Helm charts and used as the engine to deploy everything in the cluster. This gives you a high degree of control, consistency, and auditability. Fleet focuses not only on the ability to scale but provides a high degree of control and visibility to exactly what is installed on the cluster. To access Fleet, click the Continuous Delivery option in the Rancher UI. For more information, see the Fleet website.