ci(metrics): deploy metrics-collector single-replica to staging/prod#1438
Closed
chong-techops wants to merge 1 commit into
Closed
ci(metrics): deploy metrics-collector single-replica to staging/prod#1438chong-techops wants to merge 1 commit into
chong-techops wants to merge 1 commit into
Conversation
…(TECH-6484 B)
deploy/metrics-collector/{staging,prod}/values.yaml (replicaCount 1, serves
/metrics on :9090, ServiceMonitor scrapes the DB gauges from this one pod --
deterministic, no hashmod; minimal env, only DATABASE_URL) and a standalone
deploy-metrics-collector workflow (bake target + helm-deploy via the shared
techops-services/common chart, release keeperhub-metrics-collector).
Depends on TECH-6484 A (the service + image target) and on the
keeperhub-metrics-collector ECR repo existing (terraform in
techops_infrastructure). Merge only after A lands and the ECR repo is applied,
else the post-merge deploy run fails on a missing repo. Does NOT cut over: the
app's db-metrics ServiceMonitor and /api/metrics/db route stay until the
collector is verified in staging.
Author
🧹 PR Environment Cleaned UpThe PR environment has been successfully deleted. Deleted Resources:
All resources have been cleaned up and will no longer incur costs. |
ℹ️ No PR Environment to Clean UpNo PR environment was found for this PR. This is expected if:
|
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
Deploys
keeperhub-metrics-collectorsingle-replica to staging/prod (the deploy half of TECH-6484).deploy/metrics-collector/{staging,prod}/values.yaml—replicaCount: 1, serves/metricson:9090, a ServiceMonitor that scrapes the DB gauges from this one pod (deterministic, no hashmod). Minimal env: onlyDATABASE_URL..github/workflows/deploy-metrics-collector.yaml— standalone (events-style) trigger on staging/prod + dispatch; bakes themetrics-collectortarget and helm-deploys via the sharedtechops-services/commonchart (releasekeeperhub-metrics-collector, namespacekeeperhub).Do not merge yet — ordered dependencies
keeperhub-metrics-collector-{staging,prod}ECR repo existing — terraform is drafted intechops_infrastructure; the TFC workspace must be created + applied first. Otherwise the post-merge deploy run fails on a missing repo (and re-fails on later staging pushes touching the broad trigger paths).No cutover
The app's
db-metricsServiceMonitor and/api/metrics/dbroute stay in place. Cutover (remove the app monitor + env-gate the route to 404) is a later step, after the collector is verified scraping in staging.