Replies: 1 comment
-
We ran into a similar issue where the prometheus CRDs were invalid because of a race condition with loki helm chart also updating them with an older content, see grafana/loki#7488 We yet have to test the following workaround: use Flux helm post rendered with kustomize special syntax to delete each *.monitoring.coreos.com CRD from loki rendered helm output kubernetes-sigs/kustomize#1593 (comment) patches:
- target:
kind: CustomResourceDefinition
name: servicemonitors.monitoring.coreos.com
patch: |
$patch: delete
apiVersion: route.openshift.io/v1
kind: CustomResourceDefinition
metadata:
name: DOES NOT MATTER |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi!
I'm mainly trying to run a Prometheus stack via the example from here without any changes.
When I run it, the release is always not ready. It shows this error:
When I look at the cluster it seams that all pods are created and running succesfully. I can for example log into Grafana.
Anyone a hint? I followed the debug steps here: https://fluxcd.io/flux/cheatsheets/troubleshooting/#how-to-debug-not-ready-errors, but all is OK. I'm running on K3s.
Can it be the case, that it has something to do with: fluxcd/flux2-monitoring-example#29
Best regards,
Kersten
Beta Was this translation helpful? Give feedback.
All reactions