Liveliness probes fail sporadically

[jpflouret]

Steps To Reproduce

1. Install helm chart
2. Wait and watch for events

Expected Result

Liveliness probes do not fail in normal operation.

Actual Result

Liveliness probes occasionally fail. E.g.

$ kubectl -n bitwarden get events
LAST SEEN   TYPE      REASON             OBJECT                                 MESSAGE
9m11s       Normal    Killing            pod/bitwarden-api-54c5d4fbcb-kc7c5     Container bitwarden-api failed liveness probe, will be restarted
9m10s       Normal    Pulled             pod/bitwarden-api-54c5d4fbcb-kc7c5     Container image "bitwarden/api:2024.2.2" already present on machine
9m10s       Normal    Created            pod/bitwarden-api-54c5d4fbcb-kc7c5     Created container bitwarden-api
9m10s       Normal    Started            pod/bitwarden-api-54c5d4fbcb-kc7c5     Started container bitwarden-api
6m1s        Warning   Unhealthy          pod/bitwarden-api-54c5d4fbcb-kc7c5     Liveness probe failed: Get "http://10.244.3.144:5000/alive": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
4m11s       Warning   Unhealthy          pod/bitwarden-admin-58c8896cf8-7sdvc   Liveness probe failed: Get "http://10.244.3.143:5000/alive": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Screenshots or Videos

No response

Additional Context

No response

Chart Version

self-host-2024.2.2

Environment Details

• Environment: k8s
• Hardware: AMD Ryzen 7 5800X 8-Core Processor
• Cores: 8
• RAM: 16Gi (4.9Gi Used, 9.7Gi Available)

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.