Skip to content

Book III · Containers as a starship fleet

Fleet Command

Nobody Else Wanted the Job, So I Became an Overpowered Fleet Admiral

Chapter 1

Nobody Else Wanted the Bridge

The captain's chair was empty, so I sat in it. Containers became ships, and Kubernetes became the fleet that keeps them in formation across the dark. The interlude shows how the fleet keeps its ordered number of ships.

Interlude

The Self-Healing Fleet

Two squadrons, each with an ordered number of ships. Sink one, or send a change down the pipeline, and watch the fleet controller keep the order.

Fleet controller Watching the fleet

Biscuit BrigadeDesired 4Actual 4

Teapot WingDesired 3Actual 3

  • Round porthole: previous ship.
  • Diamond on a bright gold hull: new version.
  • Dashed outline: an empty berth.

Repair

  1. Hit (pending)
  2. Detect (pending)
  3. Order (pending)
  4. Launch (pending)
  5. Ready (pending)

Pull request

  1. Build (pending)
  2. Test (pending)
  3. Review (pending)
  4. Deploy (pending)

Both squadrons are at full strength: actual state matches desired state.

Chapter 2

A Fleet of Our Own

Self-hosting means the shipyard is mine too. I run the infrastructure myself, keep it tidy, and know which ship runs which service before anyone has to ask.

Chapter 3

Orders Through the Pipeline

CI/CD pipelines carry my orders out to the fleet, step by step. Every pull request gets a careful review before it launches, because an Admiral reads the plan twice.