Problems

Labs open a real Linux machine in your browser. Quizzes check the theory in a minute.

14 of 277 problems

Title	Topic	Acceptance	Difficulty	XP
Search and Replace Across Many FilesUpgrade every http:// endpoint to https:// in all config files of a tree, and only in config files.easyShell10 XP	Shell	New	easy	10
Where Should Database Data Live?You run PostgreSQL in a container. You want the data to survive docker rm and container upgrades. What should you use?easyDocker3 XP	Docker	New	easy	3
Roll Back a Broken Helm UpgradeThe latest Helm upgrade broke a release. Find the last good revision in its history and roll back to it.mediumKubernetes20 XP	Kubernetes	New	medium	20
Upgrade a Helm Release Without Losing Its SettingsMove a release to the newest chart version in the repository while keeping every custom value.mediumKubernetes20 XP	Kubernetes	New	medium	20
Unstick a Helm ReleaseEvery Helm upgrade fails with "another operation is in progress". Recover the release and finish the upgrade the team asked for.hardKubernetes40 XP	Kubernetes	New	hard	40
An Upgrade Stuck in Its HookA Helm upgrade failed because its pre-upgrade hook timed out. Find the hook that never finished, then complete the upgrade the team wanted.mediumKubernetes20 XP	Kubernetes	New	medium	20
Someone Edited a Helm Release by HandQuick kubectl fixes changed a Helm-managed app behind Helm's back. Put the objects back to what the release defines, using Helm, without uninstalling.mediumKubernetes20 XP	Kubernetes	New	medium	20
Helm Upgraded the Operator, Not Its CRDAfter upgrading an operator's chart, its new custom resource field is silently dropped. Helm doesn't upgrade CRDs from a chart's crds/ folder. Do it yourself and create the resource.mediumKubernetes20 XP	Kubernetes	New	medium	20
kubeadm Upgrade OrderYou are upgrading a kubeadm cluster by one minor version. Which order is correct for the first control-plane node?mediumKubernetes5 XP	Kubernetes	New	medium	5
Rolling Back a Helm Releasehelm upgrade shop ./chart -f prod-values.yaml broke the app. helm history shop shows the last good release is revision 3. What is the cleanest way back?easyKubernetes3 XP	Kubernetes	New	easy	3
Charts, Releases and RevisionsYou run helm install api internal/webapp -n shop, then helm upgrade api internal/webapp -n shop --set replicaCount=3. Which statement is true?easyKubernetes3 XP	Kubernetes	New	easy	3
Upgrades That Forget SettingsA release was installed with --set config.logLevel=debug. Later someone runs helm upgrade web internal/webapp --set replicaCount=3, and the log level silently gmediumKubernetes5 XP	Kubernetes	New	medium	5
Upgrades That Undo ThemselvesYou want an upgrade to roll back automatically if the new Pods never become ready within 5 minutes. Which command does that?mediumKubernetes5 XP	Kubernetes	New	medium	5
Another Operation Is in Progresshelm upgrade api ./chart fails with "another operation (install/upgrade/rollback) is in progress". helm history api shows the last revision as pending-upgrade fhardKubernetes8 XP	Kubernetes	New	hard	8