archived the channel

@Jonathan Tobe has joined the channel

yea! nicely done 😃

Thanks for sharing, @Rob Faraj! It’s actually on the front page of Hacker News at the moment! 🙂 https://news.ycombinator.com/

The AWS team wrote a great article on tracking costs in multi-tenant Amazon EKS clusters using Kubecost https://aws.amazon.com/blogs/containers/how-to-track-costs-in-multi-tenant-amazon-eks-clusters-using-kubecost/

Adding @U010XGY9B46 bot

Ohh, thanks for the introduction, @Erik Osterman (Cloud Posse)!! @Blaise Pabon, let’s talk 🙂

@Webb need any community evangelists? ☝️ 😃

FWIW, I have had an interest in k8s resource consumption and billing for about a year now. I was following the https://github.com/project-koku project for a while.

@Erik Osterman (Cloud Posse) suggested that I join this channel after I made a comment along these lines:

My employer is cutting back on open source initiatives. I am looking to join a team of people developing a disruptive technology with a global scope and a demonstrable commitment to continuous improvement.

I'm coming out of an established log aggregation vendor, so I could be immediately useful to observability vendors.

I can do anything I need to in English, Spanish and French.

Thanks @Webb

Hi @Igor Rodionov that log has indeed been moved to debug verbosity about a month ago. Our latest build should no longer contain. Anything else we can help with?

@Ajay Tripathy
We are running kubecost version 1.46.6
Because of k8s autoscaling we see a lot of log messages in cost-model container.
Like that

I0228 23:14:25.979517       1 costmodel.go:623] Node "10.102.44.77:10255" has been deleted from Kubernetes. Query historical data to get it.

How can we reduce logging noise?
If update kubecost would solve the problem?
Is there any env var that change logging verbosity ?

Hello

@UUB28NLDS help keep tabs! 😉

Sweet, let me know if we can help!

Busy looking to implement kubecost at a new company using gke

Awesomeness

@Jan we do! Here’s an invite: https://join.slack.com/t/kubecost/shared_invite/enQtNTA2MjQ1NDUyODE5LWFjYzIzNWE4MDkzMmUyZGU4NjkwMzMyMjIyM2E0NGNmYjExZjBiNjk1YzY5ZDI0ZTNhZDg4NjlkMGRkYzFlZTU
Would be great to catch up soon too.

@Webb have yiu got some other slack space or something? Seems pretty quiet in here

Glad to hear! Let me know if you have any other questions or issues.

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.

Hi @AG this is a new one for me. Is this for the prometheus-server volume itself or something else?

@here after increasing pvc for prometheus-server and restarting the pod still seeing the below error

see my answer in #kubernetes

how to encrypt passwords in helm values.yaml, any good documents is appreciated. Thanks

sure. Recently I started working on it.. will definitely post here if any question. Thanks again.

Of course! Let me know if we can help anywhere else

Thank you @Webb

Yep, it should if port is correct. Our front end (settings) will tell you if those metrics are not scraped successfully.

@Webb will it work if node-exporter running in different namespace?

You can also disable our node exporter

If it’s running on the default nodePort it should just get picked up by or Prometheus

@AG if the prometheus-node-exporter already running in the cluster, how do I use it for kubecost

very nice @Webb

much appreciated!

cheers mate

ah I see

The slack notification is a feature of AlertManager. If you are using your own Prometheus then you are also using your own AlertManager and have to configure Slack there.

any idea on the slack notification where im going wrong?

which I should probably just do

@Jan As I explained before, the setting you need is global.grafana.domainName but you are only setting grafana.domainName

that said I have not yet pulled the chart apart

I just dont seem to be able to preset those parameters (slack and grafana address)

so everything else is working fine

Thanks for sharing! You’re meaning to be using a ServiceMonitor correct? That looks like the only part I haven’t tested recently. @Jeremy G actually has a similar config I believe.

works if i set it via the kubecost site after

well it doesn't get set