asdfgugus
asdfgugus
anything new?
I support the split as well.
Looks like the same issue as here: https://github.com/opencost/opencost-ui/issues/4
Well the issue is in the [docker-entrypoint.sh](https://github.com/opencost/opencost/blob/develop/ui/docker-entrypoint.sh) script: - `cp -rv /opt/ui/dist/* /var/www` - `envsubst '$API_PORT $API_SERVER $UI_PORT' < /etc/nginx/conf.d/default.nginx.conf.template > /etc/nginx/conf.d/default.nginx.conf`
> Perhaps we would need to tweak the opencost-ui dockerfile and test on OpenShift/non-OpenShift setup I totally agree on that. We should make it read-only again.
In my setup I use an external Prometheus and deployed my own networkPolicy. Therefore I am not affected. I shortly installed Prometheus with the docs from OpenCost and both labels...
Same issue here since upgrading to v1.110.0 (Chart 1.35.0). - By mounting a volume and set the env var `CONFIG_PATH` to its mount path, the error in the logs disappeared....
My bad, I thought that you meant the error at the bottom of the logs. When initializing, OpenCost queries the `up` metrics to extract the jobs. It seems to me...
> ``` > ~ $ curl http://vmselect-victoria-metrics-k8s-stack.victoria-metrics.svc:8481/select/0/prometheus/api/v1/query?query=up > {"status":"success","isPartial":false,"data":{"resultType":"vector","result":[]},"stats":{"seriesFetched": "0","executionTimeMsec":1}} > ``` This should return the `up` metrics in the `result`. But it is empty.
Please bump the chart version