Developers on a county OKE cluster want kubectl logs and later platform collectors to see application messages from a containerized service. Where should the process write those messages?
Select an answer to reveal the explanation.
Short Explanation
On a cluster, treat logs like a live radio broadcast: write to stdout/stderr so the platform can tune in. Hiding messages in a private file inside the container is like whispering in a locked room—kubectl logs never hears them.
Full Explanation
Kubernetes and OKE collect container standard output and standard error as the primary log stream. Writing only to an in-container file hides that stream from kubectl logs and from Logging or APM plumbing that expects the container log pipeline. Prefer structured logging to stdout; leave hostPath scrapers and email relays for other concerns. Domain 5 covers OCI Logging wiring—this item is the OKE practice of emitting a stream.