Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Aliases for pods with label filters not workingΒ #3574

@FrankFoerster24

Description

@FrankFoerster24

Describe the bug
Aliases for pods with label filters stopped working somewhere in v0.50.*, at least v0.50.11 and v0.50.12. It seems similar to #3462. But simpler aliases work, "complex" don't (with an unknown definition of the term "complex").

To Reproduce
Steps to reproduce the behavior:

  1. Define aliases like:
aliases:
  pgra: pod app.kubernetes.io/name=grafana-agent
  pingress: pod app=ingress-nginx
  1. start k9s
  2. test alias :pgra
  3. observe an error popup stating < Ruroh? no resource meta defined for "pod app.kubernetes.io/name=grafana-agent" >
  4. test the alias' content :pod app.kubernetes.io/name=grafana-agent
  5. observe the expected result
  6. test the other alias :pingress
  7. observe the expected result.

Historical Documents
k9s logs this:

2025-09-22T09:30:24+02:00 INF 🐢 K9s starting up...
2025-09-22T09:30:24+02:00 INF βœ… Kubernetes connectivity OK
2025-09-22T09:30:35+02:00 WRN No resources found for v1/pods in "all" namespace
2025-09-22T09:30:45+02:00 ERR Component init failed error="no resource meta defined for\n \"pod app.kubernetes.io/name=grafana-agent\"" comp-name=""

Expected behavior
Aliases work with filter.

Screenshots
n/a, IMHO.

Versions (please complete the following information):

  • OS: Mac OSX 15.6.1
  • K9s: v0.50.12
  • K8s: v1.20.15

Additional context
n/a

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingin-progressMark issue as being worked on

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions