Skip to content
Stackship documentation Svenska

Lifecycle Manager

How the platform knows which version of each of its parts runs, where new versions come from, and how an upgrade is planned, checked, rolled out and finished.

  • After upgrading — Finish an upgrade — have a cluster administrator apply the platform admin bundle, deal with settings changed by hand, and apply the platform's access-control roles to every cluster.
  • API reference — Every HTTP endpoint of the lifecycle module: authentication, IAM action, parameters, bodies and status codes.
  • Platform backups — What the platform backs up every day, where the backups go, which backups the Backups page lists, and what its health conditions mean.
  • Manage platform backups — Take a platform backup now, change where backups go, change or pause the daily schedule, and keep a database from filling up behind a failing archive.
  • Configuration reference — Configuration keys of the lifecycle module: sections, environment variables, types and defaults.
  • Error codes — The codes the Lifecycle module refuses a request with — platform drift and platform backups — what each means, and what to do about it.
  • Lifecycle Manager — How the platform knows which version of each of its parts runs, where new versions come from, and how an upgrade is planned, checked, rolled out and finished.
  • Install a component — Install an optional backend module that is not running on this platform yet — what it requires, what the install does, and how to follow, resume or repair it.
  • Permissions — The actions that govern the Lifecycle Manager and the platform backups, and the platform roles that hold them.
  • Settings changed by hand — Find platform settings someone changed directly in the cluster, adopt them into the platform configuration, or let a release rollout put the release's values back.
  • Pre-upgrade checks — Every check the platform runs before a rollout — what it looks at, when it is skipped, what a warning or a failure means, and which failures cannot be overridden.
  • Releases and the release feed — What a platform release is, how the platform reads and verifies the signed release feed, which channel it follows, and what happens without a feed.
  • Statuses — What every status in the Lifecycle Manager means — component health, the warnings above the components, dependencies, plans, rollouts, installs, drift scans, the admin bundle and the clusters after an upgrade.
  • Upgrade the platform — Check for new releases, plan a rollout, review its batches and pre-upgrade checks, execute it, follow it, and deal with a pause, a cancellation or a rollback.