Open lorenzo-w opened 1 year ago
Could be due to insufficient compute resources on the vcluster nodes.
Seems to be due to vcluster pods prematurely deploying with wrong certificates
Workaround: scale the vcluster deployment fully down and up again.
Currently, it can happen multiple times in a row that the vcluster setup somehow crashes and leaves the entire vcluster namespace in a failed state, from which deleting the namespace and re-installing is the only recovery. This isn't exactly smooth sailing, but debugging this will be a lot of work.