You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Deploy a helm chart to a non-default namespace
Deploy another version of the helm chart so there's something to rollback to
Use the helm view to rollback to the previous version
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.
The text was updated successfully, but these errors were encountered:
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:
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):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: