Foreword
Read little, type a lot. In “Kubernetes hands-on” you took the
application notes first into a kind cluster and then onto
three VMs with RKE2, with your own chart, Gateway, drain and etcd
backup. This book starts where the question is no longer “How do I run a
cluster?” but “How do I run many?”.
SUSE’s answer is called Rancher. You learn it from the bottom up: Rancher Desktop and k3s on your laptop and a small VM, then Rancher Manager itself, which takes over an existing cluster and builds a new one on three empty VMs. After that it becomes everyday work: projects, users and permissions, your own catalog with Gitea as registry and Helm repo, GitOps with Fleet across several clusters, Longhorn for a database that can change nodes, monitoring with a real alert, upgrades, backups and access when Rancher itself goes down.
Rancher is a web UI. This book shows it to you in screenshots from
its own lab, but works with YAML and kubectl against
Rancher’s objects. That way you understand what a click really does, and
you can repeat it, version it and automate it.
The book is for platform engineers, ops and DevOps people who know Kubernetes well and are now building or taking over a platform for several teams and clusters.
The Training Rules
- Type, don’t copy. Every command once yourself.
- Compare with Expected. After each drill you see what you should get. If it differs, that is where the real lesson is.
- Pass the checkpoint. Only when the check commands show what is listed there do you move on.
- Solve the challenge on your own. First the hint, then the solution.
- Lab values stay in the lab.
lab-admin-pw-123,lab-gitea-pw-123,lab-db-pw-123and all otherlab-…values are practice data. You never print tokens, not even in the lab.
Warning: All outputs and screenshots come from real test runs. IDs like
c-m-ct8fr7hj, IP addresses, times and pod names will differ on your machine. What matters is what happens.
Structure of Each Training Day
| Section | Purpose |
|---|---|
| Briefing | The essentials in a few bullet points |
| Drills | Commands with expected output, screenshots of the UI |
| Checkpoint | Individual check commands: did everything work? |
| Challenge | A task without instructions |
| Enterprise Note | What is different in production |
The Training Plan
| Part | Day | Unit |
|---|---|---|
| 1 – Local | 0 | The training ground |
| 1 | Rancher Desktop | |
| 2 | Understanding k3s | |
| 2 – Rancher Manager | 3 | Installing Rancher Manager |
| 4 | Importing clusters | |
| 5 | Creating clusters | |
| 6 | Projects, users, roles, quotas | |
| 7 | Apps and Helm repos | |
| 3 – Fleet | 8 | Fleet: GitOps with Gitea |
| 9 | Fleet for many clusters | |
| 10 | Longhorn | |
| 11 | Monitoring | |
| 4 – Operations | 12 | Upgrades |
| 13 | Backup and restore | |
| 14 | Security and access | |
| Competition | 15 | Disaster drills |
| Appendix | A | Cheat sheet |
| B | Final exam |
The Lab
Part 1 runs on the Mac with Rancher Desktop and a small VM for k3s.
From Part 2 on, VMs via Multipass join in: rancher (4 CPUs,
8 GB) for Rancher Manager and werk1 to werk3
(2 CPUs, 3 GB each) for the cluster that Rancher builds. Recommended is
a Mac with 24 GB RAM; with 16 GB you start only werk1, and
the drain and Longhorn exercises turn out smaller. Any other Ubuntu
24.04 VM with SSH and sudo works too.
The tested versions: Rancher v2.15.3 with Fleet 0.16.3, RKE2 and k3s v1.36.5, Rancher Desktop v1.24.0, cert-manager v1.20.5, Longhorn v1.12.1, Gitea 1.27 and Helm 4.3. Rancher 2.15 supports Kubernetes up to v1.36; why that matters is shown on Day 12.
Where this book only touches on a topic, the sister books go deeper: “Kubernetes hands-on” for the fundamentals from pods to etcd, “Container tools hands-on” for images and registries, “Gateway API hands-on” for routing at the edge of the cluster.
Let’s go.