The startup probe of the authentik-server and authentik-worker pods always returns an error, which causes kubernetes to reschedule the pods.
An excerpt of the authentik-worker logs.
{"event":"checking health","level":"debug","mode":"worker","timestamp":"2024-05-30T11:24:53Z"}
{"error":"stat /dev/shm/authentik-worker: no such file or directory","event":"failed to check worker heartbeat file","level":"warning","timestamp":"2024-05-30T11:24:53Z"}
Additionally throws the authentik-server the following error message:
{"event": "Loaded app settings", "level": "debug", "logger": "authentik.lib.config", "timestamp": 1717068978.7989888, "path": "authentik.events.settings"}
{"error":"authentik starting","event":"failed to proxy to backend","level":"warning","logger":"authentik.router","timestamp":"2024-05-30T11:36:19Z"}
{"error":"authentik starting","event":"failed to proxy to backend","level":"warning","logger":"authentik.router","timestamp":"2024-05-30T11:36:29Z"}
{"error":"Get \"http://localhost:8000/-/metrics/\": dial unix /dev/shm/authentik-core.sock: connect: no such file or directory","event":"failed to get upstream metrics","level":"warning","logger":"authentik.router.metrics","timestamp":"2024-05-30T11:36:34Z"}
{"error":"Get \"http://localhost:8000/-/metrics/\": dial unix /dev/shm/authentik-core.sock: connect: no such file or directory","event":"failed to get upstream metrics","level":"warning","logger":"authentik.router.metrics","timestamp":"2024-05-30T11:36:36Z"}
{"error":"authentik starting","event":"failed to proxy to backend","level":"warning","logger":"authentik.router","timestamp":"2024-05-30T11:36:39Z"}
/ak-root/venv/lib/python3.12/site-packages/opencontainers/distribution/reggie/defaults.py:17: SyntaxWarning: invalid escape sequence '\('
"http[s]?://(?:[a-zA-Z]|[0-9]|[$-_@.&+]|[!*\(\),]|(?:%[0-9a-fA-F][0-9a-fA-F]))+"
{"error":"Get \"http://localhost:8000/-/metrics/\": dial unix /dev/shm/authentik-core.sock: connect: no such file or directory","event":"failed to get upstream metrics","level":"warning","logger":"authentik.router.metrics","timestamp":"2024-05-30T11:36:40Z"}
{"domain_url": null, "event": "Loaded MMDB database", "file": "/geoip/GeoLite2-ASN.mmdb", "last_write": 1715093837.0, "level": "info", "logger": "authentik.events.context_processors.mmdb", "pid": 17, "schema_name": "public", "timestamp": "2024-05-30T11:36:44.611828"}
{"domain_url": null, "event": "Loaded MMDB database", "file": "/geoip/GeoLite2-City.mmdb", "last_write": 1715093836.0, "level": "info", "logger": "authentik.events.context_processors.mmdb", "pid": 17, "schema_name": "public", "timestamp": "2024-05-30T11:36:44.700453"}
{"error":"authentik starting","event":"failed to proxy to backend","level":"warning","logger":"authentik.router","timestamp":"2024-05-30T11:36:49Z"}
{"error":"authentik starting","event":"failed to proxy to backend","level":"warning","logger":"authentik.router","timestamp":"2024-05-30T11:36:59Z"}
{"error":"Get \"http://localhost:8000/-/metrics/\": dial unix /dev/shm/authentik-core.sock: connect: no such file or directory","event":"failed to get upstream metrics","level":"warning","logger":"authentik.router.metrics","timestamp":"2024-05-30T11:37:04Z"}
{"error":"Get \"http://localhost:8000/-/metrics/\": dial unix /dev/shm/authentik-core.sock: connect: no such file or directory","event":"failed to get upstream metrics","level":"warning","logger":"authentik.router.metrics","timestamp":"2024-05-30T11:37:06Z"}
{"error":"authentik starting","event":"failed to proxy to backend","level":"warning","logger":"authentik.router","timestamp":"2024-05-30T11:37:09Z"}
{"error":"Get \"http://localhost:8000/-/metrics/\": dial unix /dev/shm/authentik-core.sock: connect: no such file or directory","event":"failed to get upstream metrics","level":"warning","logger":"authentik.router.metrics","timestamp":"2024-05-30T11:37:10Z"}
Expected behavior
The startup probe does not return an error. Booth applications authentik-server and authentik-worker are healthy.
Version and Deployment (please complete the following information):
authentik helm chart version: 2024.4.2
Deployment: helm
kubernetes 1.30.1
additional context
Authentik is deployed on aarch64 and x86_64 systems.
Describe the bug
The startup probe of the authentik-server and authentik-worker pods always returns an error, which causes kubernetes to reschedule the pods.
An excerpt of the authentik-worker logs.
Additionally throws the authentik-server the following error message:
Expected behavior
The startup probe does not return an error. Booth applications authentik-server and authentik-worker are healthy.
Version and Deployment (please complete the following information):
additional context
Authentik is deployed on aarch64 and x86_64 systems.
authentik-server
authentik-worker