Skip to main content
PreparationZone Logo
PrepZone

ConfigMaps, Secrets, and Ingress Routing

Externalise config, inject secrets, and route HTTP traffic with Ingress.

Pass checkpoint below

Why this matters

  • This topic directly affects how reliably BookStore reaches production — configmaps and secrets externalise bookstore config; ingress terminates http for customers..
  • Interviewers connect hands-on commands and manifests to real delivery stories, not buzzwords.
  • Later modules assume you can explain both the why and the concrete file or command involved.
  • Platform maturity shows up when teams automate this instead of relying on tribal knowledge.
InternetHTTPS request
IngressTLS + routing rules
ServiceClusterIP / LB
Podbookstore-api
Podbookstore-api
Ingress routes external HTTP to a Service, which load-balances across healthy Pods.

Externalised config

Non-secret vs Secret: BookStore engineers treat this as part of the standard path from laptop to configmaps secrets ingress readiness. Document decisions in the team runbook so on-call knows which knobs exist.

Key ideas

  • Externalised config — primary idea for configmaps-secrets-ingress
  • BookStore context — catalog API, checkout, and inventory services share the same pattern
  • Automation — prefer pipeline jobs over manual SSH steps
  • Verification — staging must prove the change before prod traffic

The rest of this guide is part of Pro

Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.

Still to come · 2 sections

  • Ingress routing
  • Production checklist

Test yourself

Answer these before moving on — recall is what makes it stick.