Dit deel is nog niet vertaald. Je ziet de Engelse tekst.
$ als gewone gebruiker# als root (of met sudo)
Get the free accounts
Most of the lab is free. Create the accounts on day one.
| Account | What you get | Note |
|---|---|---|
| Red Hat Developer Subscription for Individuals | Free RHEL 10 for up to 16 systems | Renew it every year |
| Azure free account | Credit for 30 days, 12 months of popular services, always-free services | Set a budget alert on day one |
| GitHub | Free repositories, Actions minutes, Codespaces hours | Every lab and project goes here |
| Killercoda | Free Linux and Kubernetes playgrounds in the browser | Good for quick tests and CKA scenarios |
| roadmap.sh — DevOps | A free map of the whole field | Use it to find gaps |
Let op
Cloud labs cost money when you forget them. Delete lab resource groups after each session, and keep the budget alert on.
Build two Linux machines
Two RHEL 10 virtual machines (server1, server2) cover all Linux, SSH, network and storage labs.
dnf install -y qemu-kvm libvirt virt-install
systemctl enable --now libvirtd
virt-install --name server1 --memory 2048 --vcpus 2 --disk size=20 --disk size=5 \
--location /var/lib/libvirt/images/rhel-10.0-x86_64-dvd.iso --os-variant rhel10.0 --network network=defaultThe full steps are in the lab Build your two practice servers. Take a snapshot after the install, so you can go back after every broken lab.
Prepare the Azure account
Install the tools on your Linux machine, log in, and create a budget before anything else.
rpm --import https://packages.microsoft.com/keys/microsoft.asc
dnf install -y https://packages.microsoft.com/config/rhel/10/packages-microsoft-prod.rpm
dnf install -y azure-cli
az login --use-device-code
az account show --output table
az group create --name rg-lab --location westeurope
az group delete --name rg-lab --yes --no-waitOnthoud
One resource group per lab. Deleting the group deletes everything in it — the cleanest way to stop all costs.
Set up Git and GitHub
Every script, Terraform file and pipeline lives in Git from the first day.
git config --global user.name "Your Name"
git config --global user.email "you@users.noreply.github.com"
ssh-keygen -t ed25519 -C "github"
cat ~/.ssh/id_ed25519.pub
ssh -T git@github.comAdd the public key in GitHub → Settings → SSH and GPG keys. More: Git and GitHub.
Run a local Kubernetes cluster
For phases 4 and 5 you need a cluster at home. kind (Kubernetes in containers) and k3s (a small real distribution) are both free.
curl -Lo ./kind https://kind.sigs.k8s.io/dl/latest/kind-linux-amd64
chmod +x kind && sudo mv kind /usr/local/bin/
kind create cluster --name lab
kubectl get nodes
curl -sfL https://get.k3s.io | sh -
sudo k3s kubectl get nodes| Tool | Good for |
|---|---|
| kind | Fast clusters for tests, many clusters at once, CI |
| k3s | A light "real" cluster on one or more VMs, close to production |
| kubeadm | The CKA way: build the cluster by hand (see Install a cluster) |
Keep a lab journal
Write down every lab: what you did, what broke, how you fixed it. It becomes notes, summaries, LinkedIn posts and interview stories.
- Lab status and notes: the Labs page shows my notes per lab.
- Short daily notes: IT notes and DevSecOps notes.
- Command details: Commands.