Feature Summary
Make the AKS desktop app integrate with AKS private clusters in an easier manner
Motivation
We currently have private AKS clusters and users have to connect via Azure Virtual Desktop to a vnet-linked VM to view Headlamp in a web browser
We want to make the UX as smooth as possible while not compromising on the AKS cluster being private. I believe this could be made a part of AKS Desktop
Detailed Description
From my local desktop I have access to connect to a private AKS cluster via Azure Bastion.
This generates a temporary kubeconfig in the appdata folder with server: https://localhost:generated-port/
When the terminal window is closed, the temporary kubeconfig file is deleted.
It is currently possible to manually delete the old cluster from "clusters" in AKS desktop, load it into AKS desktop, but this is a bit of a hassle, especially if you need to set explicit namespaces each time.
Ideally I would like the AKS desktop app to somehow make this experience more smooth. A refresh button or so which can consolidate use cases where the kubectx files are temporary, even though the underlying clusters are the same.
Alternatives Considered
Manually importing the temporary kubectx file each time
Checklist
Feature Summary
Make the AKS desktop app integrate with AKS private clusters in an easier manner
Motivation
We currently have private AKS clusters and users have to connect via Azure Virtual Desktop to a vnet-linked VM to view Headlamp in a web browser
We want to make the UX as smooth as possible while not compromising on the AKS cluster being private. I believe this could be made a part of AKS Desktop
Detailed Description
From my local desktop I have access to connect to a private AKS cluster via Azure Bastion.
This generates a temporary kubeconfig in the appdata folder with
server: https://localhost:generated-port/When the terminal window is closed, the temporary kubeconfig file is deleted.
It is currently possible to manually delete the old cluster from "clusters" in AKS desktop, load it into AKS desktop, but this is a bit of a hassle, especially if you need to set explicit namespaces each time.
Ideally I would like the AKS desktop app to somehow make this experience more smooth. A refresh button or so which can consolidate use cases where the kubectx files are temporary, even though the underlying clusters are the same.
Alternatives Considered
Manually importing the temporary kubectx file each time
Checklist