Fred Bricon

@dgolovin do we need to pass the flag to all oc commands or doing it once during login is sufficient?

I have indeed noticed `oc registry info` returns `docker-registry.default.svc:5000` for some contexts, which is never going to work. We cannot yet set a custom registry URL but we'll certainly work...

Well I wonder if brutally ignoring all "docker-registry.default.svc" registries would be OK. i.e. Is there a legit case where OpenShift clusters (maybe local ones?) would use docker-registry.default.svc? @dgolovin WDYT? If...

Yes that's what I think. Loading through recoil would help I think

@itsCheithanya thanks for volunteering. I did start some experiments a while ago: https://github.com/fbricon/openshift-dd-ext/commit/aeeb78aca9b5219184258206f01456bb923ec448. Code might not compile/work and still have some outstanding issues, but that should give you a good...

Session can still expire in the middle of a deployment but this change is still pretty useful. However I'd like to provide an easy path to getting a new token...

Took another look at this. Basically, I'd like to get the token url similarly to oc, which discovers it from the server url: - https://github.com/openshift/oc/blob/33f8aed30246e726258c51be27c21c60a2b005f4/pkg/helpers/tokencmd/request_token.go#L152 - https://github.com/openshift/oc/blob/33f8aed30246e726258c51be27c21c60a2b005f4/pkg/helpers/tokencmd/request_token.go#L247

Now adding button to open token url for easier login

@sshiv5768 please have at it. Basically , we need a gear icon opening a settings popup, settings would be stored in global settings

You can already copy the route URL from the last output line ('Application is exposed as: ' + route). But I think we need to use a regular div instead...