feat(observability): deploy configs as GHCR image via init container - #2
Merged
Conversation
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
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.
Summary
Dockerfile.observability-configs— a minimal Alpine image that packages all Prometheus, OTel Collector, Tempo, Loki, Promtail, and Grafana config files fromobservability/configs-initinit container in the VM compose:docker compose pullfetches the configs image from GHCR alongside api/worker, anddocker compose upruns it first to populate a named volume before the observability services startdocker compose pull+uppattern as beforeHow it works
configs-initexits after copying, all other observability services depend onservice_completed_successfully.Test plan
api,worker,observability-configs)deploy-backendjob succeedsdocker compose psshowsconfigs-initas exited (0) and all other services healthygrafana.mohith16.com