Pierre Oblin

@MShekow @FabianKramm Had issue with postgres as k3s kine backend https://github.com/k3s-io/kine/issues/63 Was better with mysql backend. Also had issue with max file descriptor (not sure how it maps in vcluster...

+1. can consistently reproduce after each stemcell upgrade. Really annoying as it locks my builds (concourse git scan stay stuck on these non existent workers)

Same requirements. And a question as a workaround: would a be possible to deploy 2 csi drivers, one csi per vcenter with local configuration. Then we could rely on distinct...

This is really a pain. Seems that vdo operator has this ability. A supported helm chart for vsphere-csi-driver would be helpfull

Missing context in your issue. Did you enable diskuuid on your vms ?

From my understanding, this is ok since 2.5.1. I was able to activate CSI without vsphere cpi

Having the same issue. Ill try to patch vanilla manifests before deploying, setting https_proxy / no_proxy env variables

Was successfull adding 2 env vars, https_proxy and no_proxy to csi-controller Deployment with the following json patch on vanilla k8s manifest: ``` - op: add path: /spec/template/spec/containers/2/env/- value: name: https_proxy...

Hello. We have the same issue. afraid their is an issue in prometheus blackbox exporter itself, that does not support correcly http/https proxy, see https://github.com/orange-cloudfoundry/paas-templates/issues/241

@Infra-Red niice. I was considering using pusher oauth2 proxy to secure our ops portails. Would you consider sharing your release in cloudfoundry-community org ? Btw, 4.0.0 has been recently released...