A tourism booking widget uses a distroless image, and operators cannot kubectl exec with bash. What is the right takeaway for application design?
Select an answer to reveal the explanation.
Short Explanation
Distroless is a locked glass case—great for production safety, terrible if you expected a picnic table and a toolbox inside. No bash is often a feature: use logs, a debug sidecar/image, or ephemeral debug workflows instead of stuffing a shell into every runtime image.
Full Explanation
Distroless and other minimal images reduce attack surface by omitting package managers and shells. Inability to exec bash is expected, not proof of cluster failure. Application teams plan observability through logs and probes, and use separate debug images or ephemeral debug containers when interactive shells are required.