Retina Windows Crashing Due to $env Being Set to C:\hpc\config on Helm Chart Redeploy

[rayaisaiah]

Describe the bug
For Retina Windows daemonset there is a bug that occurs where the env variable does not correctly set in the powershell.exe command when the helm chart is installed with an incorrect command before being uninstalled and reinstalled with a correct command.

This results in the retina-win pods crashloopbackoff'ing with the error: Error: starting daemon: creating controller-runtime manager: CreateFile C:\hpc\kubeconfig: The system cannot find the file specified.

To Reproduce
Steps to reproduce the behavior:

1. Edit the Retina Win daemonset command with the following

- powershell.exe
- -command

2. make helm-install-without-tls to install retina with hubble
3. Observe the retina-win pods crashing
4. make helm-uninstall to remove retina pods
5. Edit the Retina Win daemonset command to set the $env

- powershell.exe
- -command
- $env:CONTAINER_SANDBOX_MOUNT_POINT/controller.exe --config ./retina/config.yaml

6. make helm-install-without-tls to install retina with hubble
7. Check retina-win pod logs for the error: Error: starting daemon: creating controller-runtime manager: CreateFile C:\hpc\kubeconfig: The system cannot find the file specified.

Expected behavior
The #env variable for KUBECONFIG is incorrectly set to C:\hpc\config. The retina-win pods crashloopbackoff'ing with the error: Error: starting daemon: creating controller-runtime manager: CreateFile C:\hpc\kubeconfig: The system cannot find the file specified.

Screenshots

Platform (please complete the following information):

• OS: Windows
• Kubernetes Version: 1.28 and 1.30
• Host: AKS
• Retina Version: v0.0.20 and v0.0.17

Additional context
Discovered after testing #1118 and setting the incorrect Powershell command for the Retina Windows helm chart.

Mitigation
Configure the Retina Windows daemonset with the latest helm chart on Main and create new Windows nodes. The retina-win pods that come up will have the working powershell commands and set KUBECONFIG correctly. Alternatively create a fresh cluster and helm install the Windows daemonset with the correct commands.