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 > K3s software
For the K3s 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:
Note: When installing the node, you can point it to the respective update service, which you can do after the installation is complete using the SUSEConnect command-line tool.
To install the first K3s server on the node to be used for the Kubernetes control plane:
K3s_VERSION=""
curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=${K3s_VERSION}
INSTALL_K3S_EXEC='server --cluster-init --write-kubeconfig-mode=644' sh -s –
Note: To address availability and possible scaling to a multiple node cluster, etcd is enabled instead of using the default SQLite datastore.
To further optimize deployment factors, use the following availability practices:
FIRST_SERVER_IP="" # Private IP preferred, if available
NODE_TOKEN="" # From the /var/lib/rancher/k3s/server/node-token file on the
first server
K3s_VERSION="" # Match the first of the first server
curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=${K3s_VERSION} K3S_URL=https://${FIRST_SERVER_IP}:6443 K3S_TOKEN=${NODE_TOKEN} K3S_KUBECONFIG_MODE="644"INSTALL_K3S_EXEC='server' sh -
The K3s deployment is complete when elements of all the deployments (coredns, local-path-provisioner, metrics-server, and traefik) show at least one deployment as AVAILABLE.
By default, the K3s server nodes are available to run noncontrol-plane workloads. In this case, the K3s default behavior is perfect for the SUSE Rancher server cluster because it does not require additional agent (or “worker”) nodes to maintain a highly available SUSE Rancher server application.
Note: This can be changed to the standard Kubernetes default by adding a taint to each server node. For additional information, see the official Kubernetes documentation.
Optionally, in cases where agent nodes are wanted, run the following commands on each of the agent nodes to add it to the K3s cluster:
FIRST_SERVER_IP="" # Private IP preferred, if available
NODE_TOKEN="" # From the /var/lib/rancher/k3s/server/node-token file on the
first server
K3s_VERSION="" # Match the first of the first server
curl -sfL https://get.k3s.io | INSTALL_K3S_VERSION=${K3s_VERSION} K3S_URL=https://${FIRST_SERVER_IP}:6443 K3S_TOKEN=${NODE_TOKEN} K3S_KUBECONFIG_MODE="644" sh -