Skip to content

Track keyring convergence rollout: Phase 3 done, upstream gates #282

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
akuzminsky wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Track keyring convergence rollout: Phase 3 done, upstream gates #282

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 15 additions & 2 deletions .claude/plans/infrahouse-keyring-convergence.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -117,8 +117,9 @@ Test node: `jumphost-sincere-crawdad.rmdbkn.ci-cd.infrahouse.com`
- [x] Promote: move the change into global `modules/profile` (production has no env-local override).
Bundled with the `elastic::tls` ca-certificates fix so prod's elastic nodes never see the broken
intermediate state; all 4 touched files now byte-identical across global/dev/sandbox (invariant
from #276 restored). PR pending.
- [ ] Cut a release (merge → CD); deploy fleet-wide
from #276 restored).
- [x] Cut a release — PR [#281](https://github.com/infrahouse/puppet-code/pull/281) **merged** → CD
deploys fleet-wide.
- [ ] Watch production; spot-check long-lived instances across services (openvpn, jumphost, etc.)
- [ ] **GATE:** fleet trusts the current bundle before any signing-key retire happens upstream

Expand All @@ -130,6 +131,18 @@ This gates the upstream rotation: `terraform-aws-debian-repo` cannot switch sign
keyring refresh** (SSM run-command / ansible) is the deadline fallback, with this convergence class
as the durable follow-up.

### Critical-path items still owned by the *upstream* repo (NOT this Puppet code)

The Puppet rollout only makes the fleet **ready to trust** whatever is in the bundle. The rotation is
**not complete** until these happen upstream — as of 2026-07-04 the live `release-noble` bundle is
still **single-key** (only `A627B776…689AD619`, `[expires: 2026-07-20]`):

- [ ] **Publish the new key into the live bundle** (`terraform-aws-debian-repo` `gpg_public_keys` →
`ih-s3-reprepro export`) so `release-<codename>.infrahouse.com` serves **old + new** (dual-key).
*Only after this does the fleet's convergence actually pick up the new key.*
- [ ] Confirm the fleet has converged onto the dual-key bundle (the GATE above).
- [ ] Switch signing to the new key (dual-sign → retire old), then let the old key expire harmlessly.

## Cross-references
- Full rotation design/runbook: `terraform-aws-debian-repo/.claude/plans/gpg-key-rotation-design.local.md`
- cloud-init client behavior: `terraform-aws-cloud-init/files/bootcmd.sh`, issue infrahouse/terraform-aws-cloud-init#89
6 changes: 6 additions & 0 deletions debian/changelog
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,9 @@
puppet-code (0.1.0-1build315) noble; urgency=medium

* commit event. see changes history in git log

-- root <packager@infrahouse.com> Sat, 04 Jul 2026 13:28:00 +0000

puppet-code (0.1.0-1build314) noble; urgency=medium

* commit event. see changes history in git log
Expand Down
Loading