-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starting vcluster takes a long time and API response is slow #1900
Comments
@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:
|
@FabianKramm Shouldn't the vCluster environment use the storage product? |
@hr-tsu these are good questions. Using w/o persistence is not recommened in the majority of cases, except for maybe ephemeral workloads (i.e. CI/CD tests). But @FabianKramm merely wanted to validate if it's related to the underlying storage – which it seems to be. What I would recommend is using a different backing store in your case. By default it's sqlite with 0.20.0, which has limitations on NFS volumes. Take a look here if you want to enable persistence, but switch to a different backing store: But keep in mind that these are install time settings that cannot easily be changed after the fact. |
@heiko-braun Our current environment was using NetApp as 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.
The text was updated successfully, but these errors were encountered: