You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We updated flux 2.1.x to flux 2.2.3. Some of the kube-state-metrics alerts we had started triggering. I was able to make some changes for notification resources but we have some OCI helm charts in use that have no status reported in the kubernetes object, giving kube-state-metrics nothing to scrape a status from apparently.
Other helm repositories using https are fine, and have a fully defined status: field.
❯ flux get sources helm -A
NAMESPACE NAME REVISION SUSPENDED READY MESSAGE
...
flux-system azure-oci False True Helm repository is Ready
flux-system ww-gitops False True Helm repository is Ready
ingress-nginx ingress-nginx sha256:9c0f8ad3 False True stored artifact: revision 'sha256:9c0f8ad3'
Hi, objects that don't have any status are assumed to be ready as they have nothing to do. Their existence can be assumed as they are ready. In this case, HelmRepository of type OCI are static objects. They are not reconciled any more. #9 may be relevant here, at least the PR description. I believe that the corresponding grafana panel for readiness of objects is configured to show not ready only when the status says Ready=False explicitly.
Also, refer fluxcd/source-controller#1249 for more details about this change.
We updated flux 2.1.x to flux 2.2.3. Some of the kube-state-metrics alerts we had started triggering. I was able to make some changes for notification resources but we have some OCI helm charts in use that have no status reported in the kubernetes object, giving kube-state-metrics nothing to scrape a status from apparently.
Other helm repositories using https are fine, and have a fully defined
status:
field.We use pretty much the same kube-metrics-config as here https://github.com/fluxcd/flux2-monitoring-example/blob/main/monitoring/controllers/kube-prometheus-stack/kube-state-metrics-config.yaml
Heres a helm repo we use for the weaveworks dashboard as a public example. Note that status field is empty which seems to be the problem.
Would appreciate some advise here. Probably going to be disabling the HelmRepository monitoring for now as a workaround.
The text was updated successfully, but these errors were encountered: