aksd: fix: Respect KUBECONFIG env var when writing to kubeconfig

[tejhan]

Description

When registering an AKS cluster or trying to merge one into the kubeconfig via the project creation screen, the kubeconfig path was hardcoded to ~/.kube/config, ignoring the $KUBECONFIG environment variable. Meaning that a user with $KUBECONFIG set would have their cluster config written to the default location instead. This would happen silently & it's propagation would result in inability to create project or properly merge clusters via AKSD.

This change reads $KUBECONFIG and if it's set, uses the first path in the list (matching kubectl behavior for colon/semicolon-separated paths), falling back to ~/.kube/config only when the variable is unset.

Fixes #294

• [BUG] Cluster registration ignores $KUBECONFIG and always writes to ~/.kube/config #294

Type of Change

• [ x] Bug fix (non-breaking change which fixes an issue)
• [ x] Code refactoring

How to test:

1. Set $KUBECONFIG to non-default location
2. Attempt to create a project where the target cluster is not merged as of yet
3. Merge the cluster when notified in the project creation screen.

Results should be successful merge & next button is properly enabled.

(If this were to fail, a successful merge message would still appear but the next button would still be disabled due to merge at wrong location.)

[Copilot]

Pull request overview

This PR fixes a bug where the AKS Desktop application was ignoring the $KUBECONFIG environment variable when registering AKS clusters. Previously, the kubeconfig path was hardcoded to ~/.kube/config, which caused cluster configurations to be written to the default location even when users had $KUBECONFIG set to a different path. This resulted in silent failures during project creation when the cluster config was written to the wrong location.

Changes:

• Modified registerAKSCluster function to respect the $KUBECONFIG environment variable when determining where to write kubeconfig files
• Uses the first path from $KUBECONFIG (for colon/semicolon-separated paths), falling back to ~/.kube/config when unset

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[skoeva]

(If this were to fail, a successful merge message would still appear but the next button would still be disabled due to merge at wrong location.)

is this a bug? feel free to open an issue for this if so

[tejhan]

(If this were to fail, a successful merge message would still appear but the next button would still be disabled due to merge at wrong location.)

is this a bug? feel free to open an issue for this if so

Yes, my wording could have been better here- but this is indeed a bug, & that message describes the behavior one would notice without the fix in this PR. (If it hypothetically didn't work). I've just opened an issue with some details to track this. #294

[illume]

Thanks for this.

Can you please update the commit message to something like this?

aksd: app: aks-cluster: Respect KUBECONFIG env var when writing to kubeconfig

With the signed-off-by removed, because we're using CLA in this repo.

I linked the issue to the PR.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.