Skip to content

v0.1.4: Restart on a failed startup

Latest

Choose a tag to compare

@ecv ecv released this 18 Sep 00:51
eb2f50c

A database blip while the portal was starting used to leave it running and serving nothing, which cost nearly three hours of downtime. Startup now ends the process when a plugin cannot come up, so the pod restarts instead of sitting dead, and liveness fails once the backend has never reached ready inside its deadline.

A short database absence no longer costs a restart. Each retry opens a fresh connection, so a database that returns within thirty seconds is waited out rather than failed.

What's Changed

  • fix: Restart Backstage when startup fails to reach ready by @ecv in #82

Full Changelog: v0.1.3...v0.1.4