Kai Timmer

Anything I can do to help debug this?

> Thanks for the PR, I'm going to need to test it before merging it. I thought we'd already dealt with these, but maybe it was just the opencost-ui container....

I think that this still needs to be fixed. Even if you are not using custom pricing, but only a config like this: ``` - name: AZURE_BILLING_ACCOUNT value: "xxx" -...

@dwbrown2 You have me very surprised. I just checked a few of them (I didn't do that before I opened the issue), and all I checked had them separate. This...

> But it still seems not possible. @kaitimmer does it still work for you? Actually no, because I missed this second part. Currently, we run opencost with an exception to...

I agree, being able to control the SoC Target and maybe max SoC would be awesome.

> Did you actually try the generated rules with VictoriaMetrics? It would be great to do that. Yes, I did, and it worked fine. The VictoriaMetrics Docs state: https://docs.victoriametrics.com/victoriametrics/metricsql/ >...

When running Pyrra with VictoriaMetrics, we saw bizarre behaviour in the generic rules. This seems to be related to the recording rule chaining and to [this issue](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/860). Adding the `eval_offset`...

Since there was no progress on this one for a long time, and we switched over to use sloth, I'm closing this PR.

I also think that being able to set this option: https://github.com/kubernetes-sigs/azuredisk-csi-driver/blob/ec99ab6db2aab7d2754ec88c2a29023e8a1fa475/pkg/azuredisk/azuredisk_option.go#L99 would most likely solve this, right? However, this is not exposed anywhere and needs to be set at the...