Error while adding AWS cluster created using kube-aws + authenticated with OIDC

[AgrimPrasad]

Might be related to #13 which is also about an OIDC authenticated k8s cluster.

1. Installed kube-forwarder with brew cask install kube-forwarder
2. Upgraded awscli: aws-cli/1.16.200 Python/3.7.4 Darwin/18.6.0 botocore/1.12.190

Tried to auto-add k8s clusters configured in ~/.kube/config from the kube-forwarder UI, but was unable to do so with errors similar to ENOENT: no such file or directory, open 'preprod/ca.pem'

[lnikell]

@AgrimPrasad Thank you for your feedback, please download our latest version, we have not updated yet brew cask version of the app.

[AgrimPrasad]

@lnikell I just uninstalled the brew cask version, and then reinstalled using this link from the README: https://github.com/pixel-point/kube-forwarder/releases/latest/download/kube-forwarder.dmg

Still saw the same issue, and FWIW, both brew cask and the DMG versions seem to be v1.3.0

[lnikell]

@AgrimPrasad ok it seems that there is an issue with resolving relative paths in production build, we will investigate. For the time being i guess it will help if you change prod/ca.pem to your absolute path something like /home/alex/.kube/prod/ca.pem

[AgrimPrasad]

@lnikell Thanks for the update. I've configured the following now in ~/.kube/config:

- cluster:
    certificate-authority: /Users/agrim/.kube/preprod/ca.pem
    server: https://xxx.yyy
  name: preprod
- cluster:
    certificate-authority: /Users/agrim/.kube/prod/ca.pem
    server: https://xxx.yyy
  name: prod

However, this time the UI gets stuck on a spinner when ADD SELECTED CLUSTERS is clicked:

[proAlexandr]

@AgrimPrasad Hi, we've just released a new version. It should fix infinity loading. Could you please check it?