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

gefyra up --minikube not working when Minikube was created with a defined profile #305

Closed
Schille opened this issue Dec 14, 2022 · 2 comments · Fixed by #315
Closed

gefyra up --minikube not working when Minikube was created with a defined profile #305

Schille opened this issue Dec 14, 2022 · 2 comments · Fixed by #315
Labels
bug 🐛 Something isn't working enhancement 🎉 New feature or request

Comments

@Schille
Copy link
Collaborator

Schille commented Dec 14, 2022

What happened?

I started a Minikube cluster with the following parameters:

minikube start -p beiboot --cpus=max --memory=4000 --driver=docker --addons=default-storageclass storage-provisioner

Please mind the -p beiboot argument which creates a dedicated cluster for this particular profile. When up-ing Gefyra, it says:

> gefyra up --minikube
[CRITICAL] There was an error running Gefyra: Could not find the Minikube configuration at ~/.minikube/profiles/minikube/config.json. Did you start Minikube?

What did you expect to happen?

Well, I would expect Gefyra to tell me that no cluster is running for the default profile. However, it does not consider multiple profiles. In addition, there is no option to specify the Minikube profile I want to connect to.

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

Please see above.

What Kubernetes setup are you working with?

$ kubectl version
# paste output here

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Anything else we need to know?

No response

@Schille Schille added bug 🐛 Something isn't working enhancement 🎉 New feature or request labels Dec 14, 2022
@Schille
Copy link
Collaborator Author

Schille commented Dec 14, 2022

I just switched to the default profile with Minikube. Up-ing Gefyra was successful, but status reports no proper state:

> gefyra status
{
  "summary": "Gefyra is not running properly",
  "cluster": {
    "connected": true,
    "operator": true,
    "operator_image": "quay.io/gefyra/operator:0.13.4",
    "stowaway": true,
    "stowaway_image": "quay.io/gefyra/stowaway:0.13.4",
    "namespace": true
  },
  "client": {
    "version": "0.13.4",
    "cargo": true,
    "cargo_image": "gefyra-cargo:20221214183611",
    "network": false,
    "connection": false,
    "containers": 0,
    "bridges": 0,
    "kubeconfig": "~/.kube/config",
    "context": "minikube",
    "cargo_endpoint": "192.168.49.2:31820"
  }
}

Pinging Stowaway from the _gefyra-cargo _ (ping 192.168.99.1) is working tho.

@Schille
Copy link
Collaborator Author

Schille commented Jan 6, 2023

It seems there is a regression in Gefyra version 1.0.0. With this version the --minikube flag is not working at all. I rolled back to 0.13.4 and I can confirm it working again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something isn't working enhancement 🎉 New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant