Fabian Kramm

@MShekow Yes the problem will be the `beta`, the logs look better now, is the vcluster reachable? If not, it looks like the persistent storage in your cluster might have...

@MShekow thanks for the update! Yes we saw this type of behaviour before if the persistent volume that is used is very slow. By default, vcluster uses a local sqlite...

@MShekow Yeah to be honest I'm not exactly sure why that is not enough, thats maybe more a k3s problem, but are databases like mysql or postgresql working normally in...

@MShekow thanks for the additional information! Seems like the database is really slow (at least in the beginning) based on the k3s logs, which might trigger the too many clients...

@MShekow thanks for the information! As mentioned in the comments in the [k3s issue](https://github.com/k3s-io/k3s/issues/1459#issuecomment-829869733), k3s currently does not yet support this flag and it would need to be added first,...

@ipopovic5 thanks for creating this issue! You are correct, vcluster currently does not rewrite the secret name there, we should fix this.

@siredmar thanks for creating this issue! As discussed in slack, we could add an option to sync persistent volumes from the vcluster to the host cluster.

@felipecrs thanks for creating this issue! Yes we can add an option for this

@felipecrs unfortunately this is not possible on the `vcluster` service itself, because it is also used as Kubernetes service which requires port 443. The only workaround I see is to...

@GrahamDumpleton thanks for creating this issue! Yeah the main problem with this as you have mentioned is the RBAC the user would need to set up themselves. To be honest,...