Preflight Checklist
Describe your problem
The Login deployment uses a wait4x init container (wait-for-zitadel) to block pod startup until the Zitadel API is ready. This adds the wait4x/wait4x image as an extra dependency for what should be handled by the application itself.
Describe your ideal solution
When the Login container implements native connection retry or readiness waiting for the Zitadel backend (similar to how Zitadel supports AWAITINITIALCONN for PostgreSQL), remove the wait-for-zitadel init container and rely on the application-native mechanism instead. This is blocked until the Login container supports such a feature.
Part of #563.
Version
App version
Additional Context
Preflight Checklist
Describe your problem
The Login deployment uses a
wait4xinit container (wait-for-zitadel) to block pod startup until the Zitadel API is ready. This adds thewait4x/wait4ximage as an extra dependency for what should be handled by the application itself.Describe your ideal solution
When the Login container implements native connection retry or readiness waiting for the Zitadel backend (similar to how Zitadel supports
AWAITINITIALCONNfor PostgreSQL), remove thewait-for-zitadelinit container and rely on the application-native mechanism instead. This is blocked until the Login container supports such a feature.Part of #563.
Version
App version
Additional Context