Helm rollback uses default namespace

[joeybenamy]

Describe the bug
When a helm chart is deployed to a non-default namespace and a rollback is issued in k9s, all new resources are in the default namespace instead of the namespace of the helm chart.

To Reproduce
Steps to reproduce the behavior:

1. Deploy a helm chart to a non-default namespace
2. Deploy another version of the helm chart so there's something to rollback to
3. Use the helm view to rollback to the previous version
4. The resources created after the rollback are in the default namespace instead of the namespace for the helm chart

Historical Documents
When applicable please include any supporting artifacts: k9s debug logs, configurations, resource manifests, ...

Expected behavior
The helm chart should be rolled back to the same namespace which it was in originally

Screenshots
If applicable, add screenshots to help explain your problem.

Versions (please complete the following information):

• OS: Windows 11, WSL2
• K9s: v0.32.3
• K8s: v1.28.5-eks-5e0fdde

Additional context
Add any other context about the problem here.

[hpatel826]

I'm able to reproduce

[bbednarek]

This is serious bug which caused many issues on our production environment. It's easily reproducible on v0.32.5. Could you please prioritize fixing it?

[joeybenamy]

This is serious bug which caused many issues on our production environment. It's easily reproducible on v0.32.5. Could you please prioritize fixing it?

This is a serious issue for us as well and has caused production incidents.

[kobra4711]

@derailed it looks like there hasn't been a release since June despite this issue getting fixed - any idea when a new release will be done? mostly asking because i use brew.sh to keep things up to date rather than building things manually.