docs(ops): cutover runbook drift found during the real cutover

Open Beginner friendly
#178 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
84/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
kubernetes

Research direction

Read docs/operations/cutover.md and compare its T-1 and T-0 steps with the 2026-09-17 cutover details in this issue. Update the runbook to cover pre-issued Certificates, the required kubectl rollout restart, delta spam evaluation, and post-flip Certificate cleanup tracked in cfp-live-cluster. Done means the documented procedure matches the observed cutover.

Written by the indexing model from the issue text.

Description

Things the 2026-09-17 cutover did differently from `docs/operations/cutover.md`, to fold back in:

  • Certs are pre-issued, not issued at the flip. `mergeGateways: true` allows a hostname on one :443 listener cluster-wide, so we declared explicit `Certificate`s in `codeforphilly-ng` (cfp-live-cluster #195) before moving the listeners and the flip was instant. T-0 step 2 still says "allow a minute or two for ACME".
  • The ConfigMap change does not roll the pod. `CFP_SITE_HOST` comes via `envFrom` on a static ConfigMap; a `kubectl rollout restart` was needed after the apply. T-0 step 2 says the change "rolls the pod (Recreate strategy)".
  • The T-1 data refresh needs a spam-evaluation step for the delta (see the sibling issue), otherwise unevaluated signups reach `published`.
  • Post-flip: drop the explicit Certificate declarations so cert-manager's gateway-shim adopts the existing Secrets (tracked in cfp-live-cluster).

🤖 Generated with Claude Code

https://claude.ai/code/session_01LFyA5poHwrhAktrnsKrUiQ

Dominant language
TypeScript
Stars
1
Forks
1
Avg merge
1d 20h
Merged PRs (30d)
25

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeForPhilly/codeforphilly-ng

All issues in CodeForPhilly/codeforphilly-ng

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.