I am not entirely sure why, but it seems like the Kubelet *always* misses the first check in the readiness probe. This causes a full 60-second delay before the Authelia pod is marked as "ready," even though it was actually ready within a second of the container starting. To avoid this very long delay, during which Authelia is unreachable, even though it is working fine, we can add a startup probe with a much shorter check interval. The kubelet will not start readiness probes until the startup probe returns successfully, so it won't miss the first one any more. |
||
---|---|---|
.. | ||
authelia.yaml | ||
configuration.yml | ||
kustomization.yaml |