Maintenance, Offline Upgrades & Rollbacks #

Platform changes are governed by /v1/platform/ops/changes/* (platform_ops_changes.go) with strict offline-only artifact verification and mandatory pre-release gates.

Maintenance Windows #

Use Maintenance (POST /v1/platform/ops/changes/maintenance) to announce planned downtime windows with an explicit start time, auto-expiry duration, runbook reference, and reason. Active maintenance windows can be cancelled early via POST /v1/platform/ops/changes/maintenance/cancel.

Configuration Diff Inspection #

Inspect configuration history via GET /v1/platform/ops/changes/configs and GET /v1/platform/ops/changes/configs/diff:

  • Secret values are automatically masked using SecretRef markers so plaintext credentials never appear in diff output or audit exports.
  • Rolling back configuration requires AAL2 Step-Up authentication.

Offline Release Upgrades & Rollbacks #

TsubameMail enforces an air-gap-safe offline release policy (ErrManifestRemoteForbidden):

  1. Local Verified Manifests Only: Release upgrades (POST /v1/platform/ops/changes/releases) accept only locally staged, cryptographically verified release manifests (ErrManifestNotFound if missing). Remote image downloads or remote manifests are strictly rejected.
  2. Mandatory Pre-Release Gates: - Backup Gate (ErrReleaseBackupGateFailed): A recent verified backup must exist before upgrading. - Health Gate (ErrReleaseHealthGateFailed): Core cluster health probes must be green. - Step-Up Auth (AAL2): Operator must re-authenticate with a Passkey.
  3. Last-Known-Good Rollback: If post-upgrade verification fails, trigger POST /v1/platform/ops/changes/rollback (Step-Up gated) to revert cleanly to the last-known-good manifest version.
  4. Job Tracking: Poll GET /v1/platform/ops/changes/jobs/:id until completion.