I'm managing a Grafana Server on EKS for over 500 users who need to create and share dashboards. I use Terraform to orchestrate everything, even wrapping a Kubernetes manifest in Terraform to deploy it. The Grafana application doesn't see many changes; updates come roughly every six months. I'm wondering if there's something wrong with this setup and how I can enhance it. Do I really need tools like Flux or Argo for my situation?
5 Answers
One major concern is that Grafana's default SQLite database isn't optimal for heavy use. Switching to a dedicated database like PostgreSQL or MySQL would be a smart move if you're looking for high availability and better performance as your user base grows.
First off, figure out why you feel there's something wrong with your setup. If you're generally satisfied with it, then it might just be a matter of preference. However, if you notice drift or manage multiple environments, bringing in Argo could help streamline things for you.
Generally, using Terraform to create and deploy manifests isn’t the best practice. You might find it more manageable to adopt Flux or Argo for better deployment and configuration management.
Your setup seems solid for running a mostly-static Grafana. Just keep in mind that if you start to feel the pain of configuration drift or need to manage multiple environments, that's when tools like Argo or Flux can really shine. If you're not experiencing those issues right now, you might be good to go.
I’d consider whether you're managing dashboard lifecycles effectively. With 500 people editing dashboards, it's crucial. Look into using volume snapshots for backups or automation via dashboard tags. Also, think about setting up organizations within Grafana and perhaps adding OAuth for secure logins.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures