[stable/prometheus-operator] Errors with Helm3 #19452
Comments
Did you find any solution? I am experiencing the same error but when the installation is done I don't get the message that everything deployed fine. |
@Belonias Everything seems to be working for me. My only complain is when I change from one dashboard to the other, It asks me to save the dashboard even though I didn't change anything. Not sure if thats a bug with the dashboards, grafana or what. |
ok @shadycuz thank you for your time to reply. For me it seems the problem was EKS in GKE everything works perfect, I think that I am messing somehow in cluster creation. |
@Belonias I think I was wrong. The CRD's don't get deployed.
This means you will not be able to do lots of things the Prometheus Operator is for, like adding new services into monitoring =/. |
Can we maybe hide this hook on helm3 ? |
I have error and failed release because of this error:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
Hello, |
I'm also seeing this. Could somebody look into this please? |
Also seeing this problem, opting to install helm 2 and use it. |
Somewhat unexpectedly, I was able to install the chart with Helm 3 by setting |
Moreover in the docs for
My understanding of that is if you are using helm 3 make sure you have |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions. |
This issue is being automatically closed due to inactivity. |
Come on. Quickly support helm3 |
This works great with helm 3, what are you on about? |
When deploying... The info log doesn't matter? |
Did you read the comments, specially the one I posted like 2 comments back? |
Existence of an workaround does not mean the error does not exist, if we have to manually create CRDs and disable CRDcreation through a flag, that's not a fix. Ordered CRD Creation does need a fix for helm3. |
This issue last for more than 6 months.. and till now it is not fixed. |
Still an issue for
|
Describe the bug
When deploying the chart:
Version of Helm and Kubernetes:
Which chart:
What happened:
Errors about CRD
What you expected to happen:
No errors ;)
How to reproduce it (as minimally and precisely as possible):
Try to install chart with Helm 3.0, after some googling it appears this is a common error for charts not compatible with Helm3
Anything else we need to know:
I logged into grafana and I do see some dashboards and data looks populated but I haven't looked everything over.
The text was updated successfully, but these errors were encountered: