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.

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

[ERROR] Gefyra could not successfully confirm the Wireguard connection working. #400

Open
anovv opened this issue May 27, 2023 · 2 comments
Labels
needsmoreinfo When an issue needs more info triage To be investigated

Comments

@anovv
Copy link

anovv commented May 27, 2023

What happened?

Up: gefyra up --minikube minikube-1

Running gefyra run -i apiserver_dev:latest -N myapiserver -n default -v $(pwd):/code on minikube with colima on M2 Mac

gives:

[ERROR] Gefyra could not successfully confirm the Wireguard connection working. Please make sure you are using the --endpoint argument for remote clusters and that the Kubernetes NodePort 192.168.5.2:31820 can be reached from this machine. Please check your firewall settings, too. If you are running a local Minikube cluster, please use the 'gefyra up --minikube' flag.

What did you expect to happen?

Expected container to run inside cluster with mounted local volume

Please provide the output of gefyra check.

[INFO] Checking Docker client.
[INFO] Docker client: Ok
[INFO] Checking availability of Gefyra Cargo image...
[INFO] Gefyra Cargo: Available
[INFO] Docker: Ok
[INFO] Checking Kubernetes connection.
[INFO] Kubernetes: Ok

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

gefyra up --minikube minikube-1
gefyra run -i apiserver_dev:latest -N myapiserver -n default -v $(pwd):/code

on minikube with colima on M2 Mac

What Kubernetes setup are you working with?

minikube with colima on m2

OS version

No response

Anything else we need to know?

No response

@SteinRobert SteinRobert added the triage To be investigated label May 28, 2023
@SteinRobert
Copy link
Contributor

@dirtyValera thank you so much for reporting! Could you give tell me which version of Gefyra you're using? We recently made some changes to the determining of the cluster's endpoint - just to make sure we're investigating the correct version :)
Thank you so much again! I'm sure we'll be able to resolve this.

@SteinRobert
Copy link
Contributor

SteinRobert commented May 30, 2023

I tried to reproduce this with the minikube default profile and colima. Everything worked as expected. I'll try to create a separate profile.
Update: Also working. Here's what I did:

brew install minikube
brew install colima
colima start -m 4
minikube config set driver docker
minikube start --profile minikube-1
gefyra up --minikube minikube-1
gefyra run -i nginx:latest -N myname -n default --rm

Your error indicates that the cargo container was - for some reason - terminated between the up and run commands. There could be several reason for that. Could you please check again? Please make sure you're using the latest version of gefyra.

@SteinRobert SteinRobert added the needsmoreinfo When an issue needs more info label May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needsmoreinfo When an issue needs more info triage To be investigated
Projects
None yet
Development

No branches or pull requests

2 participants