-
-
Couldn't load subscription status.
- Fork 2k
Closed
Labels
bugSomething isn't workingSomething isn't workingin-progressMark issue as being worked onMark issue as being worked on
Description
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:
- Define aliases like:
aliases:
pgra: pod app.kubernetes.io/name=grafana-agent
pingress: pod app=ingress-nginx- start
k9s - test alias
:pgra - observe an error popup stating
< Ruroh? no resource meta defined for "pod app.kubernetes.io/name=grafana-agent" > - test the alias' content
:pod app.kubernetes.io/name=grafana-agent - observe the expected result
- test the other alias
:pingress - 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
abohne
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingin-progressMark issue as being worked onMark issue as being worked on