Search the library

Environment-based configuration generally needs replacement containers. Mounted configuration has different update behavior and the application must still reload it.

Without exec, the shell can remain as the parent process and may not forward termination signals as intended. `exec service ...` replaces the shell, making the service the main process so it receives the container stop signal directly and its exit status is reported. A wrapper supervising multiple children must explicitly forward signals and reap them.

CPU usage above a configured limit is throttled, which can increase latency without stopping the process. Memory is not throttled in the same way: crossing the container limit can cause the kernel to kill the process, often reported as OOMKilled. Requests affect scheduling and utilization-based HPA calculations, so tune all values from observed workload behavior.

Bean A needs B while B needs A, so neither constructor can complete first. Treat the exception as an ownership/design signal: extract the shared responsibility, invert a dependency, or communicate through an event. Lazy lookup can defer resolution but does not remove the cycle or its coupling.

Readiness is a traffic signal: if it fails, the pod is removed from service endpoints and users are not routed to it. Liveness is a health check for the process itself: if it fails, Kubernetes restarts the container. A pod can be alive but not ready, and that is often the correct state during startup or dependency warm-up.

A container can exhaust its CFS quota during a period even if other node CPUs are idle. Inspect container throttling counters and request/limit values alongside latency. Decide whether the limit is needed, whether requests/HPA targets match demand, or whether CPU work should be reduced; do not infer container headroom from node averages.

Multi-stage a build lets you compile in one environment and then copy only the final artifact into a slim runtime image. This reduces image size, shortens deployment time, lessens the attack surface, and makes it easier to reason about what the service actually needs to run. It is a packaging discipline, not just a size optimization.