Detect in-cluster namespace from service account file

[Copilot]

Description

When running in a Kubernetes pod, the namespace was hardcoded to "default" instead of detecting the actual namespace. This made the in-cluster context inaccurate for pods running in other namespaces.

Changes

• detectInClusterNamespace(): Reads namespace from /var/run/secrets/kubernetes.io/serviceaccount/namespace, the standard Kubernetes service account mount
• readNamespaceFromFile(): Testable helper that handles file I/O with fallback to "default" on errors (missing file, empty content)
• LoadInClusterConfig(): Uses detected namespace instead of hardcoded "default"
• Logging: Added namespace to in-cluster config load message

Example

// Before: always used "default" namespace
contextInfo.Namespace = "default"

// After: reads actual namespace from service account
namespace := detectInClusterNamespace()  // Returns "production" if pod is in production namespace
contextInfo.Namespace = namespace

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

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.