release: consolidate keeperhub pipeline into one atomic helm release#1586
Merged
Conversation
Deploy the execution pipeline (app, executor, schedule, block,
metrics-collector) as a single keeperhub-stack umbrella release instead of
five independently-triggered releases, removing the staggered-rollover window
that left in-flight executions orphaned mid-deploy.
- deploy/keeperhub-stack/{staging,prod}/values.yaml: each component nested
under its alias with nameOverride/fullnameOverride so every resource keeps
its current name (transparent to event-tracker, CI health check, runbooks)
- docker-bake.hcl: add a pipeline group so the shared builder stage builds
once instead of each deploy workflow rebuilding it independently
- build-images.yml: build the whole pipeline group in one bake session; add
workflow_dispatch for manual build-only runs
- deploy-keeperhub.yaml: deploy techops-services/keeperhub-stack atomically
- ci-pipeline.yml: single deploy job replaces the parallel app/executor jobs
- remove deploy-executor / deploy-scheduler / deploy-metrics-collector
(their build folds into build-images, their deploy into the atomic stack)
Refs KEEP-825
…b-deploys-atomic-helm ci: consolidate keeperhub pipeline into one atomic helm release
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Promote the pipeline consolidation from
stagingtoprod: the execution pipeline (app, executor, schedule, block, metrics-collector) deploys as one atomickeeperhub-stackrelease instead of five separate releases. Merged tostagingin #1585 and validated there (all five roll together in a single atomichelm upgrade).This promotion contains only the consolidation -
stagingis 2 commits ahead ofprod.Rollout - prod is a one-time cutover
Prod's five existing releases must be adopted into the single release once, before the new atomic deploy can take over. Do not treat this PR's auto-deploy as the cutover.
Recommended: merge with
[skip deploy]in the merge commit message. The prod pipeline then builds the uniform image set (needed for the cutover) but skips the deploy, leaving thekeeperhubrelease clean for the one-time adoption step. If[skip deploy]is omitted, the auto-deploy fails on Helm ownership and--atomicrolls it straight back (prod unchanged) - the manual cutover then proceeds the same way.The one-time adoption runs from the infra runbook in a low-traffic window. After it, normal prod promotions deploy the whole stack atomically.