Is it possible to use EKS in the current betas of v4 on Desktop?

[philomory]

On desktop, it is not possible to manually set up a cluster, with the app instead automatically reading cluster configuration from your KUBECONFIG file. And indeed, the application successfully detects my clusters. Also, when I open the Settings > Clusters window for the first time after each start of the application (on Windows 10), a bunch of short-lived CMD windows pop up and then disappear, executing C:\Program Files\Amazon\AWSCLIV2\aws.exe, presumably executing the auth command from the kubeconfig. However, the clusters never load and no information about any cluster is ever displayed.

The documentation within the app for the kubeconfig provider says, "Make sure that the Kubeconfig file only contains clusters and users, which are not using a Cloud Provider or OIDC for the cluster access. The import for such Kubeconfig files will fail. Please use one of the available Cloud Providers to import such clusters". I rather suspect that this is meant to apply only the the mobile version of the app, but, I'm not able to connect to these clusters either way in the v4 desktop beta.

These same clusters work just fine in the v3 version of the desktop app.

[ricoberger]

Hi @philomory, to be honest I didn't tested it until now, but on macOS it is working with the following PR #459.

Since I do not own a Windows machine, I'm didn't tested it yet. Does the Settings --> Logs view contain some useful information, which might help here?

[philomory]

The Kubenav logs are pretty sparse. After opening the app and clicking around the UI a bit, these are the entirety of the logs:

Time: 2023-01-19 13:53:25.599655
Name: KubenavDesktop _getLibraryPath
Message: Run _getLibraryPath function
Detail: -


Time: 2023-01-19 13:53:25.600660
Name: KubenavDesktop init
Message: Run init function
Detail: -


Time: 2023-01-19 13:53:28.732091
Name: KubenavDesktop kubernetesClusters
Message: Run kubernetesClusters function
Detail: -


Time: 2023-01-19 13:53:28.754864
Name: KubenavDesktop kubernetesClusters
Message: Result of the kubernetesClusters function
Detail: {"activeCluster":"test","clusters":{"AAAA":"","BBBB":"","CCCC":"","DDDD":"","EEEE":"","FFFF":"","GGGG":"","HHHH":"","test":"","IIII":""}}


Time: 2023-01-19 13:53:31.692310
Name: KubenavDesktop kubernetesRequest
Message: Run kubernetesRequest function
Detail: test, GET, /api/v1/events?fieldSelector=type=Warning, 


Time: 2023-01-19 13:54:07.361859
Name: KubenavDesktop kubernetesRequest
Message: Run kubernetesRequest function
Detail: test, GET, /api/v1/events?fieldSelector=type=Warning, 


Time: 2023-01-19 13:54:11.113279
Name: KubenavDesktop kubernetesRequest
Message: Run kubernetesRequest function
Detail: test, GET, /apis/apps/v1/deployments?, 


Time: 2023-01-19 13:54:14.018004
Name: KubenavDesktop kubernetesRequest
Message: Run kubernetesRequest function
Detail: test, GET, /api/v1/namespaces, 

Actually, looking at that, this entry seems fairly likely to be relevant:

Time: 2023-01-19 13:53:28.754864
Name: KubenavDesktop kubernetesClusters
Message: Result of the kubernetesClusters function
Detail: {"activeCluster":"test","clusters":{"AAAA":"","BBBB":"","CCCC":"","DDDD":"","EEEE":"","FFFF":"","GGGG":"","HHHH":"","test":"","IIII":""}}

While I've redacted most of the cluster names, I've not removed anything else; in particular, shouldn't the clusters map in there have a non-empty value for each key?

[philomory]

What I should try doing is setting up a non-eks cluster using e.g. minikube, and see if that one gets a different outcome.

[ricoberger]

The clusters list is generated by looping over all entries in the contexts property in the Kubeconfig file. Then we are using the name as key and the namespace as value, e.g.

contexts:
- context:
    cluster: dev-de1
    namespace: kube-system
    user: clusterAdmin_dev-de1_dev-de1
  name: dev-de1-admin

will become {"activeCluster":"dev-de1-admin","clusters":{"dev-de1-admin":"kube-system"}}, so it might be ok that the value is empty.

What is looking a bit weird for me, that there are no Result of the kubernetesRequest function logs for the Run kubernetesRequest function log lines, normally it should look like:

Time: 2023-01-20 08:46:49.527527
Name: KubenavDesktop kubernetesRequest
Message: Run kubernetesRequest function
Detail: prod-de1-admin, GET, /api/v1/namespaces/auth/pods?, 


Time: 2023-01-20 08:46:49.629852
Name: KubenavDesktop kubernetesRequest
Message: Result of the kubernetesRequest function
Detail: {"kind":"PodList","apiVersion":"v1","metadata":{"resourceVersion":"1109440783"},"items":[{"metadata":{"name":...

[ricoberger]

Hi @philomory, can you try the Windows version from https://github.com/kubenav/kubenav/actions/runs/3974844429 please. This should fix the problem.

[philomory]

So, I wasn't able to test this prior to release, but, I am happy to confirm that the issue is indeed resolved on Windows.