Fix Grafana telemetry credential delivery - #34
Merged
Conversation
syscod3
added a commit
that referenced
this pull request
Aug 11, 2026
Fix Grafana telemetry credential delivery
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.
Summary
Moves
unraid-labGrafana Cloud ingestion credentials into Bitwarden Secrets Manager and lets Argo CD reconcile themonitoring/grafana-cloudSecret.Bootstraps only the Bitwarden machine-account token through Omni and removes the legacy direct Grafana credential injector.
Validation
bash omni/scripts/inject-bitwarden-auth-token.shkubectl kustomize clusters/unraid-lab/apps/grafana-cloud-secrets/manifestsDeployment
Run
omni/scripts/inject-bitwarden-auth-token.sh --applyfrom an Omni-authenticated host after merge. Argo CD then creates the mapped credential Secret and Alloy should recover.