Skip to content

[guardian] dev-only hashi-guardian-init image for in-cluster self-heal#693

Draft
0xsiddharthks wants to merge 1 commit into
siddharth/guardian-dev-recoverfrom
siddharth/guardian-init-image
Draft

[guardian] dev-only hashi-guardian-init image for in-cluster self-heal#693
0xsiddharthks wants to merge 1 commit into
siddharth/guardian-dev-recoverfrom
siddharth/guardian-init-image

Conversation

@0xsiddharthks

Copy link
Copy Markdown
Contributor

Phase-3, dev-only. New docker/hashi-guardian-init/Containerfile that builds the hashi-guardian-init binary into a debian-slim runtime with gpg + ca-certificates.

It is the image for an in-cluster guardian self-heal CronJob (sui-operations side) that re-runs tools dev-recover after an ad-hoc guardian pod restart between deploys — recovery that today only happens on the next deploy. Same musl-static build as the sibling Containerfiles; the runtime needs gpg because dev-recover shells out to it to decrypt the ceremony KP shares.

Stacked on #692 (which adds tools dev-recover); merge after it. The Containerfile compiles (cargo check passes); the full multi-stage Docker build is unvalidated here.

Phase-3 image for an in-cluster guardian self-heal CronJob (sui-operations):
it runs `hashi-guardian-init tools dev-recover` after an ad-hoc pod restart
between deploys. Same musl-static build as the sibling Containerfiles, but a
debian-slim runtime with gpg installed, since dev-recover shells out to gpg
to decrypt the ceremony KP shares.

Stacks on the dev-recover branch (#692), which adds `tools dev-recover`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant