-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[prometheus-kube-stack] prometheus-node-exporter pod is not running through helm install #325
Comments
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. |
/reopen This issue is still present for me today in addition to other issue reporter here All versions are reported there as well |
Also can confirm this issue on Windows 10. I was able to get around it by setting
|
In more recent versions of the helm chart, the workaround property is now:
|
With the latest version of the chart, in Docker Desktop for Windows, I still had to use
to get this working. Full command:
|
Ah, ok. I just double checked and my special case is that I'm installing the |
Just to help the next person that stumbles onto this issue with Docker Desktop for windows like i did, the latest version seems to work by setting |
I am encountering this exact same issue, however I am using DockerDesktop on MacOS - 13.6.7 (22G720) - Ventura. Does anyone know of any workarounds/resolutions please? |
Managed to get around this issue by running the following command to patch the node-exporter deamon-set kubectl -n patch ds --type "json" -p '[{"op": "remove", "path" : "/spec/template/spec/containers/0/volumeMounts/2/mountPropagation"}]' |
Describe the bug
Helm install of the chart "prometheus-community/kube-prometheus-stack" in windows 10 machine is not installing "prometheus-node-exporter" pod and it is always in "CrashLoopBackOff" mode.
Version of Helm and Kubernetes:
Helm Version:
Kubernetes Version:
Which chart: kube-prometheus-stack
Which version of the chart: kube-prometheus-stack-11.0.4
prometheus-community/kube-prometheus-stack
What happened:
When I install through helm install, all the pods are running but "prometheus-node-exporter" is failed with "CrashLoopBackOff" status and the following is the error.
The log shows the following:
failed to try resolving symlinks in path "/var/log/pods/monitoring_prometheus-prometheus-node-exporter-5xxvz_591e5b9d-1f11-4418-9d44-2918fbfe66f2/node-exporter/4.log": lstat /var/log/pods/monitoring_prometheus-prometheus-node-exporter-5xxvz_591e5b9d-1f11-4418-9d44-2918fbfe66f2/node-exporter/4.log: no such file or directory
What you expected to happen:
The prometheus-node-exporter pod should run as other pods.
How to reproduce it (as minimally and precisely as possible):
Try run helm install
I tried the following command.
helm install prometheus prometheus-community/kube-prometheus-stack -n monitoring
I had windows 10 machine with latest docker desktop installed.
<~--
This could be something like:
values.yaml (only put values which differ from the defaults)
-->
Anything else we need to know:
The text was updated successfully, but these errors were encountered: