Error: Could not activate connection - When wrong context is set.

[buschNT]

What happened?

I tried to run gefyra con connect -n XXX while having an active k8s context which does not respond to the cluster I was trying to connect to. I got he following error:

"Error: Could not activate connection"

What did you expect to happen?

I was expecting that an existing gefyra connection (which was stopped) is aware of the k8s context and that it does not matter which context I am in currently. But maybe this was/is a wrong assumption.

Please provide the output of gefyra check.

-

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

Create a connection to a cluster. Stop that connection. Change the k8s context. Try to connect again.

What Kubernetes setup are you working with?

```console $ kubectl version # paste output here ```

OS version

```console # 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

[buschNT]

Right now it worked fine (I could "gefyra con connect -n ..." to a cluster while having a different context). So I am not sure what exactly triggered the error reported here.

[SteinRobert]

This was reworked in 2.1.0