Remove old workaround to append clusterUrl in resolveAuthProxyUrl()

[jim-docker]

A similar code fragment was removed in #5550. It's not clear why this code was needed. @jakolehm can you confirm if this is part of the same workaround that is no longer needed? (as stated here: #5550 (review))

fixes #5663
also may fix #5658 and fix #5628

Before this fix this was the kind of pathname going through the auth proxy:

/a412d1bafa4a0722/k8s/clusters/local/api/v1/namespaces/default/pods/nginx-deployment-9456bbbf9-6fc7k/portforward

The clusterUrl, k8s/clusters/local being extraneous and causing a Bad Gateway response.

needs more testing to confirm it doesn't cause regression tried local, spaces, aws clusters, no issues. Others should test...

[Nokel81]

I can confirm that this fixes the terminal issues.

[jansav]

This just highlights the fact that we need to add behaviours here soon. It feels like we don't know how it should work at the moment, which isn't very good thing. :)

[skri547]

@jansav should we update the lens for resolving this issue or is that expected to work in current release? We are facing the terminal issues.

[skri547]

@Nokel81 @jim-docker @jansav can you please let me know if this fixes #5829 , If yes, can we try on the same version or is that expected to upgrade lens?

[Nokel81]

@skri547 We think that this should fix that issue. You would need to upgrade Lens, but this fix has currently not been released even in an alpha.

[skri547]

@Nokel81 by when or which release it will be available for everyone? Any ETA?

[Nokel81]

Another alpha should be produced this week. With general availability in the new few weeks.

[skri547]

How can i download or upgrade the lens to Alpha to try this in Windows desktop?

[Nokel81]

When it comes out, you can change the release channel in your preferences and then "check for updates" via the tray menu.