-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bitnami/kube-prometheus fails to deploy #9270
Comments
it seems helm does not roll out the necessary crds hence these need to apply first
so probably would be nice to get it added in Read.me as pre req |
I'm afraid I'm not familiar with The CRDs are not including in the "templates" folder and they're under the |
Hi @juan131 Helmfile is based on helm3 for me at least ,. as i have helm3 installed
more docs here https://github.com/roboll/helmfile. Great the crds are here but when we apply since these are not in templates , how are these crds deployed ? in readme it specifies "Helm does not automatically upgrade or install new CRDs on a chart upgrade, so you have to install the CRDs manually before updating: " Hence that helps a lot to understand what is needed before you attempted to deploy the chart. If helm was suppose to deploy the crds then potentally i am running into a bug ??, but not sure where it comes from. |
okey i think i am running into this issue roboll/helmfile#1124 :). |
They're deployed as pure YAML manifests during the chart installation and they're ignored during Helm upgrades.
Were you able to solve the issue following the solutions proposed in that thread? |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitnami/kube-prometheus
What steps will reproduce the bug?
We are using helmfile to deploy the charts. We aare trying to apply we get the error, but when we use helmfile to invoke helm template it generates the manifets "helmfile -e sit -l name=prometheus-thanos-sidecar template"
in prometheus-values.yaml.gotmpl we have
we get error as below
Unsure if we need to deploy the CRs in cluster before we do this helm deployment.
Are you using any custom parameters or values?
values.yaml
What is the expected behavior?
We expect it to deploy the chart
What do you see instead?
erro as below
STDERR:
reading three way merge from env
Error: Failed to render chart: exit status 1: Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"]
Error: plugin "diff" exited with error
COMBINED OUTPUT:
reading three way merge from env
Error: Failed to render chart: exit status 1: Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "Prometheus" in version "monitoring.coreos.com/v1", unable to recognize "": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"]
Error: plugin "diff" exited with error
Additional information
No response
The text was updated successfully, but these errors were encountered: