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
We get our kubeconfig generated with context names in mixed case. So when we try to save csv file, it gives error as file not found. the folder in the ~/.local/state/k9s/screen-dumps/A/B is created following the mixed cased context name.. but the path mentioned in the error shows folder name with all lower case characters.
If I rename the B folder to all lower case - csv gets saved successfully.
To Reproduce
Steps to reproduce the behavior:
Rename your context in kubeconfig to container some capital letters.
Go to Deploy page in k9s and list deployments
Press Ctrl+S
See error
Expected behavior
Upton pressing Ctrl+S, csv export should be successful despite mixed cased context names in kubeconfig.
Screenshots
See error message - all lower case
See the directory name.. in caps
Versions (please complete the following information):
OS: ubuntu
K9s: v0.31.7]
K8s: v1.29.2
The text was updated successfully, but these errors were encountered:
Describe the bug
We get our kubeconfig generated with context names in mixed case. So when we try to save csv file, it gives error as file not found. the folder in the ~/.local/state/k9s/screen-dumps/A/B is created following the mixed cased context name.. but the path mentioned in the error shows folder name with all lower case characters.
If I rename the
B
folder to all lower case - csv gets saved successfully.To Reproduce
Steps to reproduce the behavior:
Deploy
page in k9s and list deploymentsExpected behavior
Upton pressing Ctrl+S, csv export should be successful despite mixed cased context names in kubeconfig.
Screenshots
See error message - all lower case
See the directory name.. in caps
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: