lifecycle: Add depends_on for worker and server container#5634
lifecycle: Add depends_on for worker and server container#5634BeryJu merged 1 commit intogoauthentik:mainfrom
Conversation
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #5634 +/- ##
==========================================
- Coverage 92.63% 92.59% -0.04%
==========================================
Files 546 546
Lines 26184 26184
==========================================
- Hits 24254 24242 -12
- Misses 1930 1942 +12
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
I couldn't find anything, I think the main reason we don't use depends_on in compose is because the authentik containers do their own healthcheck on startup, and there's no equivalent to depends_on in kubernetes, so we rather have the same logic in both places? |
|
I follow your reasoning and agree upon the build-in health checks preventing serious issues. However, to me it is not elegant that my stack sometimes starts unhealthy unnecessarily. But that does not take into account other use cases like k8s. In that perspective I understand consistency should prevail. Your call! |
* main: (58 commits) web: bump @babel/preset-env from 7.22.2 to 7.22.4 in /web (#5808) web: bump @typescript-eslint/eslint-plugin from 5.59.7 to 5.59.8 in /web (#5805) web: bump @babel/plugin-transform-runtime from 7.22.2 to 7.22.4 in /web (#5806) web: bump @typescript-eslint/parser from 5.59.7 to 5.59.8 in /web (#5807) stages/deny: fix typos (#5800) core: bump coverage from 7.2.6 to 7.2.7 (#5809) blueprints: allow setting user's passwords from blueprints (#5797) providers/proxy: add support for traefik.io API and CRD (#5801) web: fix build (#5798) web/flows: fix RedirectStage not detecting absolute URLs correctly (#5781) lifecycle: Add depends_on for worker and server container (#5634) web: bump @babel/preset-env from 7.21.5 to 7.22.2 in /web (#5791) web: bump @babel/plugin-proposal-decorators from 7.21.0 to 7.22.3 in /web (#5787) web: bump @lingui/core from 4.1.2 to 4.2.0 in /web (#5782) website: bump postcss from 8.4.23 to 8.4.24 in /website (#5783) web: bump @babel/plugin-transform-runtime from 7.21.4 to 7.22.2 in /web (#5789) core: bump goauthentik.io/api/v3 from 3.2023051.3 to 3.2023052.1 (#5788) web: bump @babel/core from 7.21.8 to 7.22.1 in /web (#5790) web: bump yaml from 2.3.0 to 2.3.1 in /web (#5792) core: bump django-otp from 1.2.0 to 1.2.1 (#5794) ...
Details
It is possible that the server or worker container start prior to redis or postgresql, rendering their health status as unhealthy. It makes sense to define an explicit start-up sequence.
No
Changes
New Features
Breaking Changes
Checklist
ak test authentik/)make lint-fix)If applicable
make website)