Matt Ray
Matt Ray
I'll try to investigate, I suspect the fix will be in opencost/opencost rather than here.
I tried to test this but was running into other issues related to 1.110.0. Everything in 1.111.0 seems to be working now, I'll try to circle back but I don't...
So to clarify, do we need to change https://github.com/opencost/opencost-helm-chart/blob/main/charts/opencost/templates/networkpolicy.yaml#L27 and https://github.com/opencost/opencost-helm-chart/blob/main/charts/opencost/templates/networkpolicy.yaml#L41 to `kubernetes.io/metadata.name: {{ .Values.networkPolicies.prometheus.namespace }}` in the templates?
We'll gladly take a PR with the change, just wanted clarification
This was fixed https://github.com/opencost/opencost-helm-chart/blob/main/charts/opencost/templates/networkpolicy.yaml#L27
Do you have a proposed solution you'd like to see in the Helm chart? I'm sure we'd merge a proper PR.
@joyartoun I'm not sure I follow, do you have a fix for the initial issue that just requires better documentation of an existing variable?
Does this need to be over in the opencost/opencost repo? Is it a Helm issue or how OpenCost works with VictoriaMetrics?
@AndrewChubatiuk should we create a VictoriaMetrics section in the docs? I think this would be pretty useful and we could position VM as a Prometheus alternative directly in the installation...
Is this a duplicate of https://github.com/opencost/opencost-helm-chart/issues/87?