Helmfile installation Step 5 does not select control-plane kube context

[pdmack]

Report incorrect documentation

Location of incorrect documentation

docs/user/helmfile-installation.md, line 761 (Step 5. Deploy the NVCF control plane components).
Same issue in docs/v0.6.0/helmfile-installation.md, line 761.

Describe the problems or issues found in the documentation

Step 5 says "Set kubectl context to your cluster" without giving a concrete command or specifying that it must be the control-plane context. In a multi-cluster setup, a bare helmfile sync targets the current kubectl context, which may be a compute cluster. The control plane silently installs to the wrong cluster.

Steps taken to verify documentation is incorrect

• Reviewed the BDD multi-cluster feature which explicitly sets the kube context before helmfile sync.
• Confirmed Steps 7 and 8 (compute-plane) already use explicit --kubeconfig flags, but Step 5 does not.

Suggested fix for documentation

Replace the one-liner with an explicit kubectl config use-context <control-plane-context> command and a kubectl config current-context verification step.

---

By submitting this issue, you agree to follow our code of conduct and our contributing guidelines.

[pdmack]

PR #252 is up. The Fern Check link checker reports 18 errors, all pre-existing on main (broken links in local-development, ngc-managed/cluster-management, user/observability, v0.6.0/observability). None are introduced by this change.