There is a Pod called
sleepy in the
Much like its faulty sibling, it experiences some trouble starting up.
Can you figure out what's wrong with
sleepy and help it achieve the Ready condition without changing the Pod images or their contents?
Hint 1 💡
As usual, it's a good idea to start by reviewing the Pod spec and the container logs.
Take a close look at the
Make sure you understand the
Examine the logs of the
Hint 2 💡
sleepy-sidecar container is supposed not to just start before the
app container but also to be fully functional.
Hint 3 💡
Kubernetes "native" sidecar containers have introduced a new container-level
What other new attributes do they bring?
Hint 4 💡
exec probe with
curl (or any other HTTP client) can be used instead of an
httpGet probe to check the container's readiness endpoint.
And for containers listening on
localhost, it might be the only option.