KOTS cli does not work when kubernetes API server has a "https://host/path/to/api" format

[SSvilen]

We use Rancher for managing our kubernetes environment.
Which means that the API Servers in the kubeconfig have the following format:
https://rancher.company.com/k8s/clusters/some-clusterid

KOTS fails to create a port forwaring to the kotsadm pod, because it drops the APIPath - in this example "k8s/clusters/some-clusterid".

I believe that the APIPath should also be extracted here and then used during the creating of the URL for the httpdialer: link

I clearly see in the Ingress and Rancher logs the APIPath being dropped. So Rancher does not know which cluster that request is for.
The result is:
Error: failed to port forward: failed to forward ports: error upgrading connection: pods "kotsadm-56475db7cb-g4lsb" not found

[jtuchscherer]

Thank you for reporting this.
We haven't tested Kots with Rancher and will put this in our backlog (can't promise if we get to it, though). But we are also very happy to accept open source contributions. Generally, we think you are on the right track with where this would have to be changed.

[SSvilen]

@jtuchscherer I'm not a go deleveoper, but I may give it a try.

[SSvilen]

PR #5254 has been opened.