REST API, mission 2 of 7
Read at start
intermediate, about 10 minutes, in the Kubernetes Simulator
Start mission
Opens once you pass Config, not code.
The briefing
orders is logging too little to debug a customer's failed checkout. Its log level comes from the LOG_LEVEL key of the orders-config ConfigMap.
kubectl edit configmap orders-config opens the live object in your editor and saves it back when you do. But a container reads its environment once, when it starts: kubectl exec POD -- printenv LOG_LEVEL shows what a running pod really has. kubectl rollout restart replaces the pods, gradually, so the new ones read the new value.
What you'll do
- Set LOG_LEVEL to debug in orders-config
- Both orders pods running with LOG_LEVEL=debug
- Bonus star: Prove it from inside: printenv LOG_LEVEL in a pod
The mission checks the cluster, not your keystrokes: any fix that works, passes.
More REST API missions
- 1. Config, not code
- 2. Read at start
- 3. CrashLoopBackOff
- 4. Ready when it's ready
- 5. Out of memory
- 6. Launch-day traffic
- 7. Rotate the password