-
Notifications
You must be signed in to change notification settings - Fork 182
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
Sort namespaces from k3s/k3d #2656
Labels
enhancement
New feature or request
Comments
skoeva
added a commit
that referenced
this issue
Dec 13, 2024
This change alphabetically sorts namespaces natively in useKubeObjectList, addressing the case where namespace lists from k3d/k3s clusters are not sorted by default. Fixes: #2656 Signed-off-by: Evangelos Skopelitis <[email protected]>
5 tasks
skoeva
added a commit
that referenced
this issue
Dec 16, 2024
This change alphabetically sorts namespaces in the UI, addressing the case where namespace lists from k3d/k3s clusters are not sorted by default. Fixes: #2656 Signed-off-by: Evangelos Skopelitis <[email protected]>
skoeva
added a commit
that referenced
this issue
Dec 16, 2024
This change alphabetically sorts namespaces in the UI, addressing the case where namespace lists from k3d/k3s clusters are not sorted by default. Fixes: #2656 Signed-off-by: Evangelos Skopelitis <[email protected]>
skoeva
added a commit
that referenced
this issue
Dec 17, 2024
This change alphabetically sorts namespaces in the UI, addressing the case where namespace lists from k3d/k3s clusters are not sorted by default. Fixes: #2656 Signed-off-by: Evangelos Skopelitis <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe the impact that the lack of the feature requested is creating.
The namespace list provided by k3s/k3d is unsorted, unlike with other platforms like kind and k0s
Describe the solution you'd like
It would be nice for this list to be alphabetically sorted
What users will benefit from this feature?
All users using k3s/k3d
Are you able to implement this feature?
I can help with this
Additional context
Slack thread describing the issue here
The text was updated successfully, but these errors were encountered: