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

k9s appends group name after already fully qualified CRD name, leading to error #3025

Open
ringods opened this issue Dec 10, 2024 · 1 comment

Comments

@ringods
Copy link

ringods commented Dec 10, 2024




Describe the bug

I’m a bit puzzled by the following. My Talos cluster doesn’t have the CSI snapshot functionality by default, so I had to install it myself.

The volume and volumegroup CRDs are installed, but when I press Enter on one of them to view the instances, for these CRDs I get an error as in the screenshot. The weird thing is that the group name is appended after an already fully qualified name. Any idea how this comes?

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'crds'
  2. Press Enter on e.g. 'volumesnapshot' CRD
  3. See error

Historical Documents

Installed these CRDs via the following instructions:

https://github.com/kubernetes-csi/external-snapshotter?tab=readme-ov-file#usage

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

Screenshot 2024-12-08 at 18 49 43

Versions (please complete the following information):

  • OS: macOS 15.1.1 (24B91)
  • K9s: v0.32.7
  • K8s: v1.31.3

Additional context
Add any other context about the problem here.

@SammyA
Copy link
Contributor

SammyA commented Dec 11, 2024

Seems to be related to #2936

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants