Pods for a marina slip-reservation app will not schedule, and the team needs control-plane scheduler and API server detail—not the app’s stdout. Which log kind answers that question?
Select an answer to reveal the explanation.
Short Explanation
Control-plane “why won’t it schedule?” lives in OKE service logs. App stdout on workers is a custom-log story—enabling one does not give you the other.
Full Explanation
When marina slip-reservation pods will not schedule, the question is control-plane behavior—API server, scheduler, and controllers—not application stdout on workers. Kubernetes Engine service logs are the log kind that covers those control-plane processes. Enabling or searching them answers why scheduling decisions fail, binding stalls, or controllers reject the workload, independent of what the app would have printed after it was Running.
Custom logs of the application’s stdout on worker nodes help once pods run and emit process output; they do not explain scheduler/API server decisions that prevented scheduling. API Gateway access logs describe front-door HTTP status for gateway traffic, not OKE control-plane scheduling. Vault audit of secret version reads tracks secret access, not why the scheduler failed to place pods.
Exam caveat: OKE service logs and worker custom logs are complementary—enable the service log category for control-plane diagnosis, and use custom logs separately for app stdout; one does not substitute for the other. Operational check: enable Kubernetes Engine service logs into a log group, reproduce the Pending/unschedulable condition, and search service-log content around scheduler/API server times before digging into worker stdout.