Visitar URL original
Cannot list custom CRD's since v0.40.1 · Issue #3116 · derailed/k9s · GitHub
Skip to content

Cannot list custom CRD's since v0.40.1 #3116

New issue
New issue
Closed
Closed
Cannot list custom CRD's since v0.40.1#3116
Labels
bugSomething isn't working

Description

@bvidovic1
bvidovic1
opened on Feb 16, 2025




Describe the bug
I upgraded k9s from v0.32.2 to v0.40.1 and since then I cannot list custom CRD's.

To Reproduce
Steps to reproduce the behavior:
Try to fetch some custom resources like externalsecrets, prometheusrule, etc.

Historical Documents

k9s logs:

11:13PM ERR Watcher failed for external-secrets.io/v1beta1/externalsecrets -- you must specify only one resource error="you must specify only one resource"
11:13PM ERR Watcher failed for external-secrets.io/v1beta1/externalsecrets -- you must specify only one resource error="you must specify only one resource"
11:13PM ERR Watcher failed for external-secrets.io/v1beta1/externalsecrets -- you must specify only one resource error="you must specify only one resource"

When I check crds, I see the ones I cannot retrieve are red:

Image

Expected behavior
Retrieved resource as in version v0.32.2.
Exact same configuration worked without any problems in version v0.32.2..

Versions (please complete the following information):

  • OS: [15.3.1]
  • K9s: [v0.40.1]
  • K8s: [1.31.3]

Additional context

😡 Watcher failed for external-secrets.io/v1beta1/externalsecrets -- you must specify only one resource

Activity

  1. isometry commented on Feb 16, 2025

    @isometry
    isometry
    on Feb 16, 2025

    I'm seeing what looks very much like the same underlying error, but with a subtly different error message:

    😡 Watcher failed for source.toolkit.fluxcd.io/v1/gitrepositories -- a resource cannot be retrieved by name across all namespaces

    I can also confirm that v0.40.0 didn't exhibit this bug.

  2. derailed commented on Feb 17, 2025

    @derailed
    derailed
    on Feb 17, 2025
    Owner

    @bvidovic1 Thank you for the heads up and @isometry Thank you for the details as this was super helpful.
    That's on me ;( Screwed up a perfectly good PR from @wjiec. Must get M'o sleep...
    Fix is (hopefully...) in the works. Let's see if we're happier on v0.40.2

  3. derailed
    closed this as completedon Feb 17, 2025

  4. junzebao commented on Feb 17, 2025

    @junzebao
    junzebao
    on Feb 17, 2025
    Image Image

    it seems to be happening still on v0.40.2.

  5. Budgiebrain994 commented on Feb 17, 2025

    @Budgiebrain994
    Budgiebrain994
    on Feb 17, 2025
    1:45PM DBG No DAO registry entry for "argoproj.io/v1alpha1/applications". Using generics!
1:45PM TRC Refresh [argoproj.io/v1alpha1/applications](0) 59.882459ms
1:45PM ERR Watcher failed for argoproj.io/v1alpha1/applications -- a resource cannot be retrieved by name across all namespaces error="a resource cannot be retrieved by name across all namespaces"
1:45PM ERR refresh failed for gvr: argoproj.io/v1alpha1/applications error="a resource cannot be retrieved by name across all namespaces"

    I'm getting the same error as @junzebao , but the error is a different one than the initial ticket.

    Same version v0.40.2

  6. derailed
    reopened this on Feb 17, 2025

  7. derailed commented on Feb 17, 2025

    @derailed
    derailed
    on Feb 17, 2025
    Owner

    Thank you all for piping in. Doh My bad ;( Apologizes for the inconvenience.
    Found the issue! Problem was between the chair and the keyboard...
    Rebuilding v0.40.2 now. If that's still a dud will push v0.40.3 in a bit (just in case...)
    Thank you all for your patience and reports!

    Please lmk if we are happier on v0.40.2/3. Tx!!

  8. derailed
    added
    bugSomething isn't working
    on Feb 17, 2025

  9. Budgiebrain994 commented on Feb 17, 2025

    @Budgiebrain994
    Budgiebrain994
    on Feb 17, 2025

    Hooray! The fix worked. I can now see CRDs.

    Thanks for all your hard work @derailed ! Hope you get some extra sleep soon.

  10. derailed commented on Feb 17, 2025

    @derailed
    derailed
    on Feb 17, 2025
    Owner

    @Budgiebrain994 Good to hear. Thank you for reporting back!
    Indeed running on fumes here at the ranch ;(

  11. derailed
    closed this as completedon Feb 17, 2025

  12. bvidovic1 commented on Feb 17, 2025

    @bvidovic1
    bvidovic1
    on Feb 17, 2025
    Author

    @derailed thanks for the prompt response and the fix.

  13. bvidovic1 commented on Feb 17, 2025

    @bvidovic1
    bvidovic1
    on Feb 17, 2025
    Author

    @derailed just a comment, I am not getting error anymore, but I cannot see externalsecrets CRD in the k9s. When I perform kubectl command I retrieve them succesfully.

  14. wpbeckwith commented on Feb 17, 2025

    @wpbeckwith
    wpbeckwith
    on Feb 17, 2025

    v0.40.3 doesn't allow me to open ANY of the k8s Gateway API classes, https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.2.1/experimental-install.yaml.

    Image

  15. rtim75 commented on Feb 17, 2025

    @rtim75
    rtim75
    on Feb 17, 2025
    Contributor

    v0.40.3 doesn't allow me to open ANY of the k8s Gateway API classes, https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.2.1/experimental-install.yaml.

    Observing the same behaviour with:

    Nonetheless, thank you for amazing work and congratz on the custom columns milestone. Love what you do

  16. Loki-Afro commented on Feb 18, 2025

    @Loki-Afro
    Loki-Afro
    on Feb 18, 2025
    Sponsor

    @derailed

    1. ~16:30 today got an issue, unable to list crd bla
    2. shortly after found this issue, already fixed, so fast? awesome
    3. hmm no new rpm available (using fedora)
    4. looked at copr build status thingy, build is just in progress, that very moment
    5. 20 min later (did something else) dnf upgrade --refresh, new k9s version
    6. k9s, best k8s client today, works as usual
    7. writing @derailed big thank you!
  17. tmeijn
    added a commit that references this issue on Feb 25, 2025

    build(deps): update derailed/k9s to v0.40.5

    b2fb428

  18. sebafo commented on Dec 4, 2025

    @sebafo
    sebafo
    on Dec 4, 2025

    v0.40.3 doesn't allow me to open ANY of the k8s Gateway API classes, https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.2.1/experimental-install.yaml.

    Image

    I have the same issue with v.0.50.16

  19. tim-goto commented on Feb 24, 2026

    @tim-goto
    tim-goto
    on Feb 24, 2026

    For me it often happens when I develop controllers and I remove and add the crds again, it usually helps to wait for a couple of minutes, then the crds are accessible in k9s (just to add another datapoint beyond a +1..)

    Also thank you very much for developing and maintaining this great tool :)

  20. codrutpanea commented on Jun 16, 2026

    @codrutpanea
    codrutpanea
    on Jun 16, 2026

    If i have k9s open and i install some crds i am not able to display them with e.g :externalsecrets. I need to close k9s and open it again for the command to work

  21. wpbeckwith commented on Jun 16, 2026

    @wpbeckwith
    wpbeckwith
    on Jun 16, 2026

    For me it often happens when I develop controllers and I remove and add the crds again, it usually helps to wait for a couple of minutes, then the crds are accessible in k9s (just to add another datapoint beyond a +1..)

    Also thank you very much for developing and maintaining this great tool :)

    I would expect the refresh to fix this. There does seem to be some non-deterministic limit to when they will be available. Even if I new it was 3m, then I could switch off to some other task until then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions