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 I tried to shell connect to the default container of a pod, that is, on the Pods page pressing "S", the program crashed. This seems new after upgrading to v3.20.0.
To Reproduce
Steps to reproduce the behavior:
Go to 'Pods' page
Select a pod that has multiple containers (singular container works fine)
This commit fixes a bug introcuded in v0.32.0 where the shell-in and
attach commands would fail with a nil pointer exception for pods with
more than one container.
Resolvesderailed#2585
Describe the bug
When I tried to shell connect to the default container of a pod, that is, on the Pods page pressing "S", the program crashed. This seems new after upgrading to
v3.20.0
.To Reproduce
Steps to reproduce the behavior:
Historical Documents
Error log:
Expected behavior
k9s selects the default container and establish a shell to it.
Screenshots
Not applicable
Versions (please complete the following information):
Additional context
If I remember correctly, in
3.19.x
or before versions there was no such bug.The text was updated successfully, but these errors were encountered: