Multiplayer game server, mission 6 of 7

Saves that survive

advanced, about 10 minutes, in the Kubernetes Simulator

Start mission

Opens once you pass Stranded.

The briefing

From Dana Kowalski, on-call lead at Larchwood (a fictional company)

Tonight's maintenance replaces the arena StatefulSet, and the runbook says to delete its claims too, to start clean. The last time we did that, every match save went with them.

Before anyone touches it: make sure no save can be lost however tonight goes. Don't run the maintenance yourself — just make it safe.

What you'll do

  • Every arena save volume is kept if its claim is deleted
  • …and arena still running all three servers on them
  • Bonus star: Delete nothing on the way

The mission checks the cluster, not your keystrokes: any fix that works, passes.

Concepts

  • Reclaim policy

    What happens to a PersistentVolume when its claim is deleted. Delete, the default for dynamically provisioned volumes such as kind's standard class, removes the volume and its data. Retain keeps both: the volume becomes Released and waits for someone to decide. It's a field on the volume, so it can be changed while the volume is in use.

    Read the Kubernetes docs

More Multiplayer game server missions

  1. 1. Every server has a name
  2. 2. Saves that survive
  3. 3. One server first
  4. 4. Don't empty the arena
  5. 5. Stranded
  6. 6. Saves that survive
  7. 7. Claim it back
Every Kubernetes Simulator mission

AboutGuidesCompare

PrivacyCookiesTerms

Hackademy is a trading name of Mather Software Ltd, registered in England and Wales, company number 17443861. ICO registration ZC256628.

Contact: support@mathersoftware.com© 2026 Mather Software Ltd