1. Since there is no Traefik as an ingress controller, choose the right version of the Nginx Ingress Controller for supporting K3s. In this PoC, it is version 1.1.0. It will create an ingress-nginx namespace. Also, you will need a patch for this deployment using a DNS load balancer.

Copy
$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.1.0/deploy/static/provider/baremetal/deploy.yaml

$ cat > ingress.yaml <<EOF 
spec:
  template:
    spec:
      hostNetwork: true
EOF

$ kubectl patch deployment ingress-nginx-controller -n ingress-nginx --patch "$(cat ingress.yaml)"
deployment.apps/ingress-nginx-controller patched

2. In the DNS load balancer use case, increase the number of ingress-nginx-controller pods to 3 by editing the “replicas” to 3.

Copy
$ kubectl get deployment -n ingress-nginx
NAME                       READY   UP-TO-DATE   AVAILABLE   AGE
ingress-nginx-controller   1/1     1            1           19s
$ kubectl edit deployment ingress-nginx-controller -n ingress-nginx
...
#
apiVersion: apps/v1
kind: Deployment
metadata:
  annotations:
    deployment.kubernetes.io/revision: "2"
..
  generation: 8
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/instance: ingress-nginx
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/version: 1.1.0
    helm.sh/chart: ingress-nginx-4.0.10
  name: ingress-nginx-controller
  namespace: ingress-nginx
..
spec:
  progressDeadlineSeconds: 600
  replicas: 3      #### <--- here
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      app.kubernetes.io/component: controller
      app.kubernetes.io/instance: ingress-nginx
      app.kubernetes.io/name: ingress-nginx
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        app.kubernetes.io/component: controller
        app.kubernetes.io/instance: ingress-nginx
        app.kubernetes.io/name: ingress-nginx

3. Verify the deployment update is complete and ensure an ingress-nginx-controller is on each node.

Copy
$ kubectl get deployment  -n ingress-nginx
NAME                       READY   UP-TO-DATE   AVAILABLE   AGE
ingress-nginx-controller   3/3     3            3           1m
$ kubectl get pods -n ingress-nginx
NAME                                        READY   STATUS      RESTARTS   AGE
ingress-nginx-admission-create-jm5nd        0/1     Completed   0          1m
ingress-nginx-admission-patch-c8wt8         0/1     Completed   1          1m
ingress-nginx-controller-7b8496bf47-59r5q   1/1     Running     0          50s
ingress-nginx-controller-7b8496bf47-ltp6r   1/1     Running     0          50s
ingress-nginx-controller-7b8496bf47-vm5hs   1/1     Running     0          1m
$ kubectl get pods -n ingress-nginx -o wide
NAME                                        READY   STATUS      RESTARTS   AGE     IP             NODE                 NOMINATED NODE   READINESS GATES
ingress-nginx-admission-create-jm5nd        0/1     Completed   0          2m   10.42.2.4      node3.k3s.hhii.amp   <none>           <none>
ingress-nginx-admission-patch-c8wt8         0/1     Completed   1          2m   10.42.2.5      node3.k3s.hhii.amp   <none>           <none>
ingress-nginx-controller-7b8496bf47-59r5q   1/1     Running     0          1m   10.76.85.101   node1.k3s.hhii.amp   <none>           <none>
ingress-nginx-controller-7b8496bf47-ltp6r   1/1     Running     0          1m   10.76.85.102   node2.k3s.hhii.amp   <none>           <none>
ingress-nginx-controller-7b8496bf47-vm5hs   1/1     Running     0          2m   10.76.85.103   node3.k3s.hhii.amp   <none>           <none>

Note: For other instructions, create a new namespace like nginx-ingress for all namespaces or pre-defined namespaces. In this case, the ingress-nginx namespace is created and used.

In this instruction, use docker to run the rancher v2.6.4 container image on ports 443 and 80 by referring to the following steps. Note: A bootstrap password is required to access the Rancher web UI. For the production, run Rancher on a 3-node K8s cluster for High Availability (HA) instead of a single node or VM with docker.

Copy
$ sudo docker run -d --restart=unless-stopped   -p 80:80 -p 443:443 --name rancher26  --privileged   rancher/rancher:latest 
$ docker ps 
CONTAINER ID   IMAGE                    COMMAND           CREATED         STATUS         PORTS                                                                      NAMES
fbf6db201863   rancher/rancher:latest   "entrypoint.sh"   2 minutes ago   Up 2 minutes   0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp   rancher26

$ docker logs rancher26 2>&1 | grep "Bootstrap Password"
2022/05/11 03:47:24 [INFO] Bootstrap Password: xxxxxxxxxxxxxxxxxxxx

1. Login to Rancher web UI. Click Import Existing.

Figure 2: Rancher - Dashboard of Clusters

2. Click Generic.

Figure 3: Import K3s as a Generic Kubernetes to Rancher

3. Enter the Cluster Name and Description.

Figure 4: Import Generic Information

4. Refer to the following command to import k3s cluster to the Rancher:

Copy
$ curl --insecure -sfL https://10.76.85.165/v3/import/
xxxxx7wq6rrrpjft4gvzblksc9xzjchvl22xxxx_c-m-9xrzlsg4.yaml | kubectl apply -f -
clusterrole.rbac.authorization.k8s.io/proxy-clusterrole-kubeapiserver created
clusterrolebinding.rbac.authorization.k8s.io/proxy-role-binding-kubernetes-master created
namespace/cattle-system created
serviceaccount/cattle created
clusterrolebinding.rbac.authorization.k8s.io/cattle-admin-binding created
secret/cattle-credentials-b36fb99 created
clusterrole.rbac.authorization.k8s.io/cattle-admin created
Warning:
spec.template.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSel
ectorTerms[0].matchExpressions[0].key: beta.kubernetes.io/os is deprecated since v1.14; use
"kubernetes.io/os" instead
deployment.apps/cattle-cluster-agent created
service/cattle-cluster-agent created

5. After a few minutes, the cluster appears on the dashboard.

Figure 5: List of Clusters on the Dashboard

6. In the cluster view, there are 3 nodes with the Kubernetes version 1.23.6+k3s1.

Figure 6: Nodes Page

1. For a clean deployment, clean up the target storage(s) for the Longhorn storage cluster using the following script with root permission. Note: You can add more storage devices in the loop if needed.

Copy
$ sudo su -
$ for DISK in "/dev/nvme1n1" "/dev/nvme2n1" "/dev/nvme3n1" ;
do echo $DISK && \
sgdisk --zap-all $DISK && \
dd if=/dev/zero of="$DISK" bs=1M count=100 oflag=direct,dsync && \
blkdiscard $DISK
done

2. Make partitions on target storage(s) and format the partitions in xfs.

Copy
$ sudo fdisk /dev/nvme1n1
$ sudo fdisk /dev/nvme2n1
$ sudo mkfs.xfs /dev/nvme1n1p1 -f
$ sudo mkfs.xfs /dev/nvme2n1p1 -f

3. Create mount points and edit /etc/fstab for the mount points.

Copy
$ sudo mkdir -p /var/lib/longhorn
$ sudo mkdir -p /var/lib/longhorn2
$ sudo vi /etc/fstab
##add the line below
/dev/nvme1n1p1 /var/lib/longhorn xfs defaults 0 1
/dev/nvme2n1p1 /var/lib/longhorn2 xfs defaults 0 1
## save the file and quit vi editor

4. Mount the storage devices to the mount points.

Copy
$ sudo mount /var/lib/longhorn/
$ sudo mount /var/lib/longhorn2/

5. Click Longhorn from Apps & Marketplace > Charts to install Longhorn charts for block storage.

Figure 7: Charts Tab

6. For servers provisioned with SLE Micro;

• Ensure open-iscsi has been installed.
• iscsid daemon is running on all nodes of the Kubernetes cluster. If not, execute the following command to install:

Copy
$ sudo transactional-update pkg install open-iscsi
## after installation complete
$ sudo reboot

7. Click Install to deploy the Longhorn charts.

Figure 8: Longhorn Charts Deployment

8. After choosing the preferred customization on Step 2 page, click Install to complete the deployment. There will be a chart console showing up the deployment process on Rancher.

Figure 9: Longhorn Charts Deployment: Step 2

9. Once the deployment is completed, the Longhorn page appears on the left-side navigation bar. Click Longhorn.

Figure 10: Longhorn Overview Page

10. The Longhorn storage console opens on another tab. Click Node for adding the drives to the Longhorn cluster.

Figure 11: Dashboard Tab of the Longhorn Console

11. For node 1 from the Operation column drop-down, click Edit node and disks to add the second drive on each to the Longhorn cluster.

Figure 12: Node Tab of the Longhorn Console

12. A dialog window appears for the node.

• Click Add Disk.
• Enter the name of the disk. For example, node1-disk1.
• Enter the path (/var/lib/longhorn2/) for the new drive mounted.
• Select Enable under Scheduling to make the new drive functional in the cluster.
• Click Save.

Figure 13: Dialog Window for the Node

13. Once it saves the new drive information, the Node tab displays the updated node's capacity.

Figure 14: Node Tab of the Longhorn Console with the Updated Node’s Capacity

14. Repeat steps 11 - 13 for the other nodes.

Figure 15: Dialog Window for Other Node

Figure 16: Node Tab of the Longhorn Console with the Updated Node’s Capacity

15. Once the new drives are added to the cluster, the Dashboard displays the total storage capacity to be scheduled in the Longhorn cluster.

Figure 17: Dashboard Tab of the Longhorn Console with the Total Storage Capacity

16. If you add new drives for each node later, mount them on /var/lib/longhorn3 and repeat steps 11 - 13 to extend the storage capacity.

Prerequisite: Ensure Longhorn service is up and running to enable persistent volumes for Prometheus and Grafana.

1. Click Monitoring from Apps & Marketplace > Charts to install Monitoring charts.

Figure 18: Charts Tab to Install Monitoring

2. Click Install to deploy the Monitoring charts.

Figure 19: Monitoring Charts Deployment

3. Under Edit Options tab enter the preferred customization on Step 2 page. Click Install to complete the deployment.

Figure 20: Monitoring Charts Deployment: Step 2

4. To configure Prometheus option,

• Check Persistent Storage for Prometheus.
• Choose longhorn from the Storage Class Name drop-down.

Figure 21: Prometheus Configuration

5. To configure Grafana option,

• Check Enable with PVC Template.
• Enter 50Gi as the Size field.
• Choose longhorn from the Storage Class Name drop-down.
• Choose ReadWriteOnce” from the Access Mode drop-down.
• Click Next to Step 3.

Figure 22: Grafana Configuration

6. On Step 3, review the check boxes for additional deployment options and the timeout option. Click Install.

Figure 23: Additional Deployment Options

7. During installation, the Installed Apps page appears with the installation status.

Figure 24: Installed Apps Page with Installation Status

a. Check Longhorn Dashboard, you will see 2 volumes In Progress.

Figure 25: Longhorn Dashboard

8. When the installation is complete, a SUCCESS message appears on the Installed Apps page.

Figure 26: Installed Apps Page with the Success Message

9. The Monitoring page appears on the left-side navigation bar. Click Monitoring to access the Dashboard.

Figure 27: Dashboard of Monitoring

10. Click Grafana.

11. The Grafana web application opens on a new tab of the browser.

Figure 28: Grafana Web Console

12. After a few minutes, the charts display the history of telemetries and utilizations.

Figure 29: Grafana Charts with Telemetries and Utilizations Data

Notes:

• If you want to re-install K3s on any node, clean up the node by uninstalling K3s and the drives for Longhorn storage service:

Copy
$ sudo su -
$ /usr/local/bin/k3s-uninstall.sh
$ umount /dev/nvme1n1 /dev/nvme2n1 /dev/nvme3n1
$ for DISK in "/dev/nvme1n1" "/dev/nvme2n1" "/dev/nvme3n1" ;
do echo $DISK && \
sgdisk --zap-all $DISK && \
dd if=/dev/zero of="$DISK" bs=1M count=100 oflag=direct,dsync && \
blkdiscard $DISK
done

• If you install K3s on SLE Micro v5.1 or later, reboot the system to complete the transaction update.

Copy
$ reboot

• The cluster is gracefully shutdown by the following steps:

a.Login to the nodes through SSH or cockpit web console.
b.For root privileges, execute the sudo command.

Copy
$ sudo su -
#

c. Shutdown K3s on each node.

Copy
# k3s-killall.sh

d. Wait for the script to complete its jobs.
e. Shutdown the nodes by entering:

Copy
# poweroff

or

Copy
# shutdown -h now

The rancher console displays the state of the cluster is Unavailable.
Figure 30: Rancher Console