Skip to content
beskid Beskid

Beskid

Jump to a Beskid service

Beskid

Jump to a Beskid service

Operate the Platform

Store runtime credentials in OpenBao and registry publication credentials in protected Woodpecker secrets. Do not print, commit, copy, or reuse either secret.

Identify the Woodpecker source commit and the standalone production Compose host. Obtain production access only through the approved operator process.

  1. Review Containers.
  2. Identify the required images and volumes.
  3. Follow Verify production delivery with the immutable sha-* image identities from Woodpecker.
  4. Verify Health and monitoring after Watchtower reconciles the controlled tags.

Application services run from controlled production tags while matching immutable sha-* tags provide audit and rollback identity. Persistent volumes remain attached across Watchtower reconciliation.

If a required build or publish check fails, Woodpecker stops and reports the failure. Preserve its URL, commit, status, and image evidence. The production operator owns restore or rollback by registry retagging and Watchtower control. After recovery, repeat production verification.

Inspect the container contract.