zitadel icon indicating copy to clipboard operation
zitadel copied to clipboard

Reduce startup times

Open eliobischof opened this issue 2 years ago • 4 comments

For being able to scale more reactively, reduced startup times could help.

One way of achieving that could be to separate init and start phases.

eliobischof avatar May 03 '22 11:05 eliobischof

to reduce the startup time even more, we might change the order in ZITADEL itself as well (listen before starting projections) will have to check if possible

livio-a avatar May 03 '22 13:05 livio-a

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] avatar Aug 09 '22 15:08 stale[bot]

@eliobischof can this one be closed?

adlerhurst avatar Sep 05 '22 19:09 adlerhurst

@eliobischof can this one be closed?

No. Moved the issue to needs more info, added the question label and a better title and description.

eliobischof avatar Sep 05 '22 19:09 eliobischof

@fforootd @livio-a FYI, terraform-provider-google doesn't support cloud run jobs, yet. https://github.com/hashicorp/terraform-provider-google/issues/11743

eliobischof avatar Oct 23 '22 12:10 eliobischof

Hm, thats a bummer, in that case we need to think of something else 😁

fforootd avatar Oct 24 '22 17:10 fforootd

Maybe we can run a cloud run job using the gcloud terraform provider https://github.com/terraform-google-modules/terraform-google-gcloud

@livio-a , when we deploy an init/setup job using a newer image tag, is the old revision still allowed to serve traffic during the job execution?

eliobischof avatar Oct 25 '22 13:10 eliobischof

The old revision must serve traffic until the new is ready IMO it might even make sense to then gradually swift traffic from the old to the new revision

livio-a avatar Oct 25 '22 13:10 livio-a