O. Matskiv

Results 117 comments of O. Matskiv

I had a quick look at the code. The info message in question gets printed by `configLoader.SetDevSpaceRoot()` that's called from `cmd.getCommands()` here - https://github.com/loft-sh/devspace/blob/a5eac169596719ace76d4824fb8e1b085581dc25/cmd/run.go#L206 I couldn't quickly come up with...

I just bumped into the same issue for the first time ever(in like 9 month of vcluster development with devspace). It also got resolved by re-running. No idea what is...

@guettli I don't think it matters if you use devspace 5.x or 6.x at the moment. Currently, devspace.yaml uses configuration version that is supported by both 5.x and 6.x. I...

I had this happen with a different project, and it was caused by the OOM kill by the cgroup, because the pod had a quite low memory limit. The default...

Me and @pratikjagrut discussed a possible refactor of GH actions. Proposed new setup: - a build action which will build the syncer image and push it to a public accessible...

@FabianKramm We would have an automated clean-up job that will trigger on PR merge. A separate ghcr.io/loft-sh/vcluster-dev package sounds good to me.

There could be an alternative solution - when particular toleration is enforced by vcluster, then the nodes synced by vcluster should have the taints modified based on the enforced toleration....

Hello @skhota I am not sure why did Helm report pre-install error. Seems like pre-install pod succeeded. Can you check if the `vc10-1-job` Kubernetes Job reported a successful status? Your...

If you can reproduce pre-install error issue, please try installing vcluster with helm ([see "helm" tab in this doc](https://www.vcluster.com/docs/getting-started/deployment)) and run helm install it with `--debug` flag. If the issue...

Unfortunately, you can not run helm by copying the command that was printed by vcluster. Please follow the instructions on the helm tab on this docs page to run it...