Whenever a new release is pushed, the service returns "503 Service Unavailable" for a few minutes. I believe this is because the server needs to pull and cache all podcasts before serving traffic, but K8s has no way of knowing when the server is ready. A probe would fix that problem.
Whenever a new release is pushed, the service returns "503 Service Unavailable" for a few minutes. I believe this is because the server needs to pull and cache all podcasts before serving traffic, but K8s has no way of knowing when the server is ready. A probe would fix that problem.