Matheus Pimenta
Matheus Pimenta
We could have a different flag that uses the defaults as well
We have `.spec.driftDetection.mode` `warn`: https://fluxcd.io/flux/components/helm/helmreleases/#drift-detection We send an event to notification-controller when a drift is detected, so you can choose any of these notification providers to send the alert to:...
You can plot alert graphs in Grafana, have you tried setting up Alertmanager as a data source? https://grafana.com/docs/grafana/latest/datasources/alertmanager/
You can have one Provider+Alert per namespace
Have you checked Flux Operator `ResourceSet` API? It helps you reduce Flux boilerplate a lot, many people are happy with that: https://fluxcd.control-plane.io/operator/resourcesets/introduction/
Check also a reference architecture here: https://fluxcd.control-plane.io/guides/d2-architecture-reference/
> failed to decode Kubernetes YAML from /tmp/kustomization-3934915096/operator/Chart.yaml: missing kind in object {{v2 } {{ } map[] map[]}} This means you have a Helm chart in the manifests from the...
I think the cache metrics should have specific names based on *use case*, and not specifically kind. Each use case will most likely always have a specific kind associated with,...
Same for `flux diff artifact`
> There may be other reasons why we want a shim API within our own namespace (maybe so Notification controller only has to watch a single Kind of list), but...