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
It appears version v0.25.21 introduced an issue when leaving the Helm values view (or after hitting enter on a release) and going back to the Helm releases view. Only the release for which you check the values is showing up.
To Reproduce
Steps to reproduce the behavior:
Go to the Helm releases view (with more than a single release) :helm
View the values for a release v
Exit the values view esc
See that there is now only a single release shown.
Expected behavior
All releases are still shown
Screenshots
If applicable, add screenshots to help explain your problem.
Versions (please complete the following information):
OS: Darwin ARM64
K9s: v0.25.21
K8s: v1.22.5
Additional context
I'm looking into it currently. After some very early investigation, looks like it's a result of the changes to the EnsureHelmConfig function in dao/helm.go. Digging deeper.
The text was updated successfully, but these errors were encountered:
j2udev
changed the title
Helm releases view broken after viewing values for a particular release in v0.25.21
Helm releases view broken after interacting with a particular release in v0.25.21
Jul 13, 2022
j2udev
changed the title
Helm releases view broken after interacting with a particular release in v0.25.21
Helm releases view broken after interacting with a release in v0.25.21
Jul 13, 2022
Describe the bug
It appears version v0.25.21 introduced an issue when leaving the Helm values view (or after hitting
enter
on a release) and going back to the Helm releases view. Only the release for which you check the values is showing up.To Reproduce
Steps to reproduce the behavior:
:helm
v
esc
Expected behavior
All releases are still shown
Screenshots
If applicable, add screenshots to help explain your problem.
Versions (please complete the following information):
Additional context
I'm looking into it currently. After some very early investigation, looks like it's a result of the changes to the
EnsureHelmConfig
function in dao/helm.go. Digging deeper.The text was updated successfully, but these errors were encountered: