Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Helm rollback uses default namespace #2634

Open
joeybenamy opened this issue Mar 19, 2024 · 1 comment · May be fixed by #2652
Open

Helm rollback uses default namespace #2634

joeybenamy opened this issue Mar 19, 2024 · 1 comment · May be fixed by #2652
Labels
bug Something isn't working

Comments

@joeybenamy
Copy link

joeybenamy commented Mar 19, 2024




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
Copy link

I'm able to reproduce

@derailed derailed added the bug Something isn't working label Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants