Ajay Tripathy

In https://github.com/opencost/opencost/pull/1813 , we've started to open source more recording rules + fallbacks so we can get all this data into the opencost FE via recording rule-- more coming soon!

Thanks for the feedback. I think we should incorporate the above helm chart changes as well as look to integrate the authentication library in an upcoming release. I've tagged this...

Yes it would...however this may be out of scope since the plan of opencost is not to support cloud-provider specific pricing long term-- it's a better fit for the community...

https://github.com/kubecost/cost-analyzer-helm-chart/issues/1869 Let's move tracking here. This is sort-of beyond the scope of opencost.

Hey @akosveres "unable to get addresses:" and "unable to get disks" is a separate warning for additional functionality not required for core opencost operation nor for spot nodes. We'll look...

Hey @boniek83 happy to support this. Want to open a separate issue to track and so we can add more information?

As some additional context @boniek83 when we first added gpu support there weren't amd/intel k8s device plugins, but would love to find out more if there are!

Hi @gillg I think this makes a lot of sense and we can just parse the node / pod labels to come up with a price. Tentatively suggesting for v1.101

Hey @Pokom that would be awesome! I'm going to tag this as v1.101 tentatively-- do you think you can get this in before our v1.101 release March 7th? If not...

No worries @Pokom -- we'll let you know by unassigning if we have to pick it up on our end!