O. Matskiv

k3s maintainers [decided to not expose the database connection flags](https://github.com/k3s-io/k3s/issues/1459#issuecomment-1167703296), I don't think we can influence or work around that so I'll close this issue, but feel free to comment...

The technical blockers for logging that Fabian described in his comment have been recently resolved(#694) and documented. Expect them to be available in the next release (0.13.0). [New docs](https://www.vcluster.com/docs/operator/monitoring-logging#logging) describe...

There has not been a response on this issue in a long time so I will close it. We can reopen if more information is provided.

Since the v0.12.0 the IngressClasses are synced from vcluster to the host, so you could create one in vcluster and mark it as the default one. Combined with the ["init...

Seems like the question was answered, so I'll close this issue. If you have follow-up questions - don't hesitate to open another issue or to reach out to us in...

@ddl-risong-na The fix was not released yet, but we just merged it, so it will be part of the next release.

Actually, I think it makes sense to close this now, as the fix was merged already. We can obviously reopen if the new version doesn't fix the problem.

@ericjee vcluster CLI has two commands that might work for your use case. Instead of deleting the vcluster you could pause it: ``` Usage: vcluster [command] ... pause Pauses a...

@ericjee Do the `vcluster pause` and `vcluster resume` commands that I mentioned in the previous comment satisfy your use case?

Since the v0.5.0 release, this is almost fully supported. The only exception is an edge case where the `namespaceSelector` is combined with the `namespaces` field in the same affinity term.