Clint Mod
Clint Mod
> As a workaround, are you able to provision dedicated volumes for each Prometheus, or is that too much overhead? That would be a work around but is too much...
@simonpasquier I actually did take a look at that and try it but there's no way to set the subpath on the Prometheus crd. I also tried patching the prometheus...
Not sure that would work… here's what my current prometheus def looks like: ``` 02/10/22 09:44:55.004 ~/c/g/f/till[1] k -n kube-system get prometheus/prometheus-stack-kube-prom-prometheus -o yaml apiVersion: monitoring.coreos.com/v1 kind: Prometheus metadata: annotations:...
also… in the code I mentioned in my top most post… it won't matter what we set the subpath to in yaml… it's hard coded in the go code
Added a PR with how a simple fix might look.
@simonpasquier I would like to report that this actually worked and I will probably use this in the interim to work around the problem. I do still think you should...
Here was the full workaround: ``` kubectl -n kube-system patch \ prometheus prometheus-stack-kube-prom-prometheus \ --type=merge \ --patch-file helm/kube-prometheus/patches/subpath.yaml ``` contents of `helm/kube-prometheus/patches/subpath.yaml` ``` spec: containers: - name: prometheus volumeMounts: -...
The test is mostly cut and paste from the one above it with the exeception of setting the sub path to `/asdf`
@thaJeztah Is this true that a /24 is no longer required for an overlay network? If so let me know and I can work on a PR for the docs....
seems like a dup of #41483 and fixed in #44571