Skip to content
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.

Sign up for GitHub

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

Jump to bottom

vcluster create <name> blocks execution or command does not finish... #2189

Open
jakoberpf opened this issue Sep 30, 2024 · 3 comments
Open

vcluster create <name> blocks execution or command does not finish... #2189

jakoberpf opened this issue Sep 30, 2024 · 3 comments
Labels
kind/bug

Comments

@jakoberpf
Copy link

What happened?

When running vcluster create <name> from a Gitlab runner the create commands does not end.

Screenshot 2024-09-30 at 19 28 56

What did you expect to happen?

The vcluster is create and the command continues or ends.

How can we reproduce it (as minimally and precisely as possible)?

Run vcluster create <name> from a Gitlab runner.

Anything else we need to know?

The same command works fine on the same cluster but run from my local machine. MacOS, vcluster installed with brew, same version.

Host cluster Kubernetes version

Client Version: v1.31.0
Kustomize Version: v5.4.2
Server Version: v1.28.12-eks-a18cd3a
WARNING: version difference between client (1.31) and server (1.28) exceeds the supported minor version skew of +/-1

vcluster version

vcluster version 0.20.0

VCluster Config

No special config used...
@FabianKramm
Copy link
Member

@jakoberpf thanks for creating this issue! The problem is that the gitlab runner doesn't have docker installed so vcluster CLI does port-forwarding here (although I agree the messaging is not clear), which blocks the execution. If you do not want to "connect" to the vcluster after creating it you could just run the create command with --connect=false to avoid blocking execution.

@FabianKramm FabianKramm mentioned this issue Oct 1, 2024
Merged
@jakoberpf
Copy link
Author

@FabianKramm that a great explanation thanks. One more question though. I missed to also state that the vcluster is created on a EKS cluster. Being the fact that we are creating the vcluster on a remote EKS, why is docker need on the gitlab runner for the vcluster cli?

@FabianKramm
Copy link
Member

@jakoberpf it's needed to start a proxy in the background to forward the connection to the vCluster. If your vCluster is reachable by other means in the gitlab runner, you can also use the --server flag in vcluster connect to not start the background proxy, another option would be to create a load balancer via --expose. All options are described here: https://vcluster.com/docs/vcluster/manage/accessing-vcluster#expose-vcluster

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@FabianKramm @jakoberpf