Fix SetCurrentContext to handle in-cluster configurations

[Copilot]

Description

SetCurrentContext attempted to update the kubeconfig file for all contexts, including in-cluster configurations where ConfigPath is empty. This caused file read errors when switching to in-cluster contexts.

Changes

• cluster/manager.go: Added check to skip kubeconfig file update when ConfigPath is empty

  if contextInfo.ConfigPath != "" {
      if err := cm.updateKubeconfigCurrentContext(contextName, contextInfo.ConfigPath); err != nil {
          return fmt.Errorf("failed to update kubeconfig file: %w", err)
      }
  }

• cluster/manager_test.go: Added test testSetCurrentContextWithEmptyConfigPath to verify context switching works for in-cluster configurations

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.