Open hr-tsu opened 3 days ago
@hr-tsu thanks for creating this issue! Are you using NFS or similar as a backing store for the vCluster? These slow SQL queries show that the underlying storage seems to be slow. To check that you can turn off persistence via:
controlPlane:
statefulSet:
persistence:
volumeClaim:
enabled: false
@FabianKramm Thanks for the comment. The storage product was in this environment, so I put in the settings you gave me and re-created it, and it was created immediately, just like the Minikube environment.
Shouldn't the vCluster environment use the storage product? Will I keep having the same problem if I use the storage product?
What happened?
When I run the vcluster create command, the command keeps waiting until the timeout, and then an error occurs.
However, the process seems to be continuing after the error, and after waiting for 2~3h, coredns are created on the host and the vcluster seems to have started (vcluster statefulsets are also running).
When I try to connect to the created vCluster and create a pod, the API takes quite a long time to respond, which interferes with the creation of the pod.
What did you expect to happen?
In another environment, the response is coming in at this rate, so I would like it to be that way. The following log environment is the Minikube environment.
How can we reproduce it (as minimally and precisely as possible)?
% vcluster create vlsuter-debug
% kubectl apply -f https://k8s.io/examples/application/deployment.yaml deployment.apps/nginx-deployment created
Anything else we need to know?
No response
Host cluster Kubernetes version
vcluster version
VCluster Config
No settings.