Dustin
3439ce1f13
Now that Victoria Metrics is hosted in Kubernetes, it only makes sense to host Grafana there as well. I chose to use a single-instance deployment for simplicity; I don't really need high availability for Grafana. Its configuration does not change enough to worry about the downtime associated with restarting it. Migrating the existing data from SQLite to PostgreSQL, while possible, is just not worth the hassle. |
||
|---|---|---|
| .. | ||
| applications | ||
| README.md | ||
| hooks.yaml | ||
| ingress.yaml | ||
| kustomization.yaml | ||
| namespace.yaml | ||
| oidc.config | ||
| policy.csv | ||
README.md
Argo CD
Argo CD is a declarative GitOps continuous delivery tool, which allows developers to define and control deployment of Kubernetes application resources from within their existing Git workflow.
kubectl apply -k argocd
kubectl apply -f argocd/applications
Components
Argo CD consists of several components, some of which are not used:
- Application Controller
- Repository Service
- Web Server
- Notification Controller
- ApplicationSet Controller1
- Dex Server2
Applications
Applications are the core resource in Argo CD. They form a collection of resources associated with a particular application deployment. They are themselves defined as Kubernetes resources (see applications).
Git Webhook
Argo CD will automatically refresh the desired state of applications whenever a changeset is pushed to the Git repository where manifests are stored. The infra/kubernetes repository has a Webhook configured in Gitea that notifies the Argo CD server on Git push events.