#kubecost (2019-10)
Kubernetes resource and cost management
Archive: https://archive.sweetops.com/kubecost/
2019-10-08
![AG avatar](https://secure.gravatar.com/avatar/2916fe1aad42f5f98c3b48b39d67efc0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0022-72.png)
@AG if the prometheus-node-exporter already running in the cluster, how do I use it for kubecost
![webb avatar](https://avatars.slack-edge.com/2019-08-27/742331234246_ca91cf7fd5e88f4206b0_72.png)
If it’s running on the default nodePort it should just get picked up by or Prometheus
![webb avatar](https://avatars.slack-edge.com/2019-08-27/742331234246_ca91cf7fd5e88f4206b0_72.png)
You can also disable our node exporter
![AG avatar](https://secure.gravatar.com/avatar/2916fe1aad42f5f98c3b48b39d67efc0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0022-72.png)
@webb will it work if node-exporter running in different namespace?
![webb avatar](https://avatars.slack-edge.com/2019-08-27/742331234246_ca91cf7fd5e88f4206b0_72.png)
Yep, it should if port is correct. Our front end (settings) will tell you if those metrics are not scraped successfully.
![AG avatar](https://secure.gravatar.com/avatar/2916fe1aad42f5f98c3b48b39d67efc0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0022-72.png)
Thank you @webb
![webb avatar](https://avatars.slack-edge.com/2019-08-27/742331234246_ca91cf7fd5e88f4206b0_72.png)
Of course! Let me know if we can help anywhere else
![AG avatar](https://secure.gravatar.com/avatar/2916fe1aad42f5f98c3b48b39d67efc0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0022-72.png)
sure. Recently I started working on it.. will definitely post here if any question. Thanks again.
2019-10-10
![AG avatar](https://secure.gravatar.com/avatar/2916fe1aad42f5f98c3b48b39d67efc0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0022-72.png)
how to encrypt passwords in helm values.yaml, any good documents is appreciated. Thanks
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
see my answer in #kubernetes
2019-10-22
![AG avatar](https://secure.gravatar.com/avatar/2916fe1aad42f5f98c3b48b39d67efc0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0022-72.png)
@here after increasing pvc for prometheus-server and restarting the pod still seeing the below error
![AG avatar](https://secure.gravatar.com/avatar/2916fe1aad42f5f98c3b48b39d67efc0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0022-72.png)
err="opening storage failed: zero-pad torn page: write /data/wal/00001581: no space left on device"
2019-10-31
![webb avatar](https://avatars.slack-edge.com/2019-08-27/742331234246_ca91cf7fd5e88f4206b0_72.png)
Hi @AG this is a new one for me. Is this for the prometheus-server volume itself or something else?
![AG avatar](https://secure.gravatar.com/avatar/2916fe1aad42f5f98c3b48b39d67efc0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0022-72.png)
Hi @webb it is resolved now. It was the problem with PVC where its not updating the volume size. worked when re-increased the size.
![webb avatar](https://avatars.slack-edge.com/2019-08-27/742331234246_ca91cf7fd5e88f4206b0_72.png)
Glad to hear! Let me know if you have any other questions or issues.