-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using GitOps with Grafana Operator to create Grafana Dashboard with Flux. #164
Conversation
This looks good @elamaran11, how do we validate this? |
@bonclay7 Just run it as is. It will work and you can validate a new dashboard getting created. |
@elamaran11 To fully validate this, maybe we should drop this in terraform? so we are sure the operator set it up correctly? And this too? |
So I went ahead and did it, I dropped the dashboard provided by Terraform but for some reason the operator can't renew my API key, maybe i'm doing something wrong?
|
@bonclay7 Dropping is not required both boards can coexist for now. |
@bonclay7 The Grafana Key is in the Secrets Manager which is expired. Operator wont renew keys with AMG. The external secrets will take care of refreshing secrets manager key with k8s secret for grafana operator but operator has to take care of refreshing grafana keys with below : export GO_AMG_API_KEY=$(aws grafana create-workspace-api-key \
--key-name "grafana-operator-key" \
--key-role "ADMIN" \
--seconds-to-live 432000 \
--workspace-id <YOUR_WORKSPACE_ID> \
--query key \
--output text)
export GO_API_KEY_SECRET_NAME=$(aws secretsmanager list-secrets \
--query 'SecretList[1].Name' | tr -d '"')
aws secretsmanager update-secret \
--secret-id $GO_API_KEY_SECRET_NAME \
--secret-string "${GO_AMG_API_KEY}" \
--region $GO_AWS_REGION |
Did I miss these instructions in the docs, or we are waiting for the full move to make it clear? |
Yes, but for customers using latest, they would be quite confused that we have two data sources and duplicates dashboards. I would suggest that we make it more seamless |
This is same as how you upgrade the Grafana Keys today. We can add these instructions after full move |
@bonclay7 Grafana Folder works now with Grafana Operator. So i have migrated all the 6 dashboards for EKS Monitoring Module to Grafana Operator and Flux with GitOps. I think we can seamlessly move other pattern dashboards and cleanup as subsequent work in future PRs. Please take this forward and let me know if you have questions. |
Added an operational procedure as well under |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome job @elamaran11. There is a few cleanup to do after this one, and docs updates
What does this PR do?
🛑 Please open an issue first to discuss any significant work and flesh out details/direction - we would hate for your time to be wasted. Consult the CONTRIBUTING guide for submitting pull-requests.
Motivation
Using GitOps with Grafana Operator to create Grafana Dashboard with Flux.
More
pre-commit run -a
with this PRNote: Not all the PRs required examples and docs.
For Moderators
Additional Notes