reinoud/flux2-hub-spoke-example
1
0
Fork 0
mirror of https://github.com/fluxcd/flux2-hub-spoke-example.git synced 2025-07-27 15:53:19 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add monitoring section to docs

Browse source 
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
This commit is contained in:
Stefan Prodan 2024-04-11 11:41:19 +03:00
parent 39ea5a4a3f
commit 45e655f7db
No known key found for this signature in database
GPG key ID: 3299AEB0E4085BAF
1 changed files with 15 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

16
README.md
View file

@ -143,7 +143,7 @@ ingress-nginx 4.10.0 False True
podinfo 6.6.2 False True podinfo 6.6.2 False True
``` ```
> [!NOTE] > [!TIP]
> Note that Flux detects changes made directly in-cluster on the objects managed > Note that Flux detects changes made directly in-cluster on the objects managed
> by a HelmRelease and automatically [corrects the drift](https://fluxcd.io/flux/components/helm/helmreleases/#drift-detection). > by a HelmRelease and automatically [corrects the drift](https://fluxcd.io/flux/components/helm/helmreleases/#drift-detection).
> During an incident or for debugging purposes, you can manually suspend the reconciliation > During an incident or for debugging purposes, you can manually suspend the reconciliation
@ -234,6 +234,20 @@ To enforce the RBAC restrictions, and to provision the controllers before the cu
3. `infra-configs` (cluster-wide custom resources - depends on `infra-controllers`) 3. `infra-configs` (cluster-wide custom resources - depends on `infra-controllers`)
4. `apps` (app workloads - depends on `infra-configs`) 4. `apps` (app workloads - depends on `infra-configs`)
> [!TIP]
> When managing a large numbers of tenants and clusters, it is recommended to use run a dedicated
> Flux instance for each group of clusters belonging to the same tenant. For more information
> on how to assign Flux instances to specific clusters, see the
> [Flux sharding and horizontal scaling guide](https://fluxcd.io/flux/installation/configuration/sharding/).
## Monitoring and alerting
To configure Prometheus, Loki and Grafana for monitoring the Flux controllers and the workloads reconciliation,
see the [monitoring example repository](https://github.com/fluxcd/flux2-monitoring-example).
To configure Flux to send events for Slack, Teams, Discord, Sentry and others external system,
you can follow the [alerting guide](https://fluxcd.io/flux/monitoring/alerts/).
## Testing ## Testing
After making changes to the manifests, you can validate them locally with [kubeconform](https://github.com/yannh/kubeconform) by running: After making changes to the manifests, you can validate them locally with [kubeconform](https://github.com/yannh/kubeconform) by running: