fix: Return error from GetDefaultKubeConfigPath instead of calling os.Exit

[YadavAkhileshh]

Summary

GetDefaultKubeConfigPath() in backend/pkg/config/config.go was calling os.Exit(1) directly when it failed to resolve the current OS user. This is a Go anti-pattern for library code utility functions should return errors and let the caller decide how to handle failure.

This PR refactors the function to return (string, error) and updates all callers accordingly.

Related Issue

Fixes #5493

Changes

• Changed GetDefaultKubeConfigPath() signature from string to (string, error).
• Replaced os.Exit(1) with a proper error return.
• Updated all callers in config.go and test files to handle the returned error.

Testing

1. Run backend tests: cd backend && go test ./pkg/config/... ./pkg/kubeconfig/... ./cmd/...
2. Start Headlamp normally and verify kubeconfig loads correctly.
3. Confirm no regression in cluster connection behavior.

[Copilot]

Pull request overview

Refactors the backend config.GetDefaultKubeConfigPath helper to return an error instead of terminating the process, and updates callers/tests to handle the new (string, error) signature. This aligns the config utility layer with Go library best practices and avoids unrecoverable exits during tests or reuse.

Changes:

• Changed GetDefaultKubeConfigPath() to return (string, error) and removed the direct os.Exit(1) call.
• Updated setKubeConfigPath and Parse to propagate kubeconfig path resolution errors.
• Updated backend tests that call GetDefaultKubeConfigPath to handle the returned error.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
backend/pkg/config/config.go	Convert default kubeconfig path resolution to error-returning flow and propagate it through config parsing.
backend/pkg/kubeconfig/kubeconfig_test.go	Update integration test to handle new (string, error) signature.
backend/cmd/headlamp_test.go	Update tests to resolve kubeconfig path once and pass it through, handling errors.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

[illume]

Thanks for working on this.

Looks like the backend tests are failing in CI. Can you check with cd backend && go test ./... and fix the errors?

How to run the backend tests

Run cd backend && go test ./... to see all failures. Fix the failing tests and commit the result.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

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

[illume]

Thanks for the contribution.

There are some open Copilot review comments — could you take a look at them? Please mark each one as resolved once you've addressed it.

[illume]

Thanks for the contribution.

Could you take a look at the commit messages in this PR? We follow a Linux kernel style for git commits — see the contributing guide and git log for examples.

Commits that need attention

• fix: Return error from GetDefaultKubeConfigPath instead of calling os.Exit — Missing area: description prefix — e.g. frontend: HomeButton: Fix so it navigates to home or backend: config: Add enable-dynamic-clusters flag.

Commit guidelines

• Use atomic commits focused on a single change.
• Use the title format <area>: <Description of changes> — description must start with a capital letter.
• Keep the title under 72 characters (soft requirement).
• Explain the intention and why the change is needed.
• Make commit titles meaningful and describe what changed.
• Do not add code that a later commit rewrites; squash or reorder commits instead.
• Do not include Fixes #NN in commit messages.

Good examples:

• frontend: HomeButton: Fix so it navigates to home
• backend: config: Add enable-dynamic-clusters flag

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

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

[illume]

Thanks for working on this.

Would you mind addressing the open Copilot review comments? Please mark each comment as resolved after addressing it.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

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

[illume]

Thanks for these changes.

Can you please address the open review comments? Once you've resolved each one, please mark it as resolved.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.

[illume]

🎉 thanks!

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: illume, YadavAkhileshh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [illume]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment