Christian Busch

> I also run into https://github.com/gefyrahq/gefyra/issues/107 while bridging. Same issue here. `gefyra unbridge --all` does not seem to have any effect after #107 . `gefyra unbridge --name ...` neither though....

I managed to solve the terminating issue of `gefyra down` by removing the `operator.gefyra.dev/kopf-finalizer` from the Finalizers of the `interceptrequests.gefyra.dev` resource. Not sure if that's super clean, though, meaning if...

I totally agree with the `--target` option. Makes sense to replace the four options with one. Furthermore it would be consistent with the `---env-from` option. Not sure if I would...

I often encounter the following logs during debugging, which makes it quite difficult to find interesting logs:  I think it would be better if these log...

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...

I think it is fine. Once issue #161 is solved and the context works as expected, `deck install` should almost never show all decks available. The command would consider the...

> Since the cli only supports one "upped" cluster at a time I feel like the given project could be set to the context implicitly, couldn't it? Yes we could,...

@SteinRobert @schwobaseggl > Feel free to add more commands for which a login should not be necessary. Not sure if this question makes sense, but why do we need a...

As far as i see, the login/auth mechanism isn't directly enforced for many commands. However, we heavily rely on GraphQL requests, which require to be logged in. Thus we would...

Note: Maybe we should also think about shortening the "unikube-" cluster prefix to something like "u-", "uk-", etc. . Alternatively we could also discuss using the ID as cluster name.