Describe the bug
We have a cluster with 13k pods in a single namespace. When I start k9s in that namespace, it can take minutes for the pods to load and for the terminal to become responsive once again, although there is a lot of latency/stutter. I understand that 13k pods are not very common, and it would be totally fine to say that that is outside the scope of what k9s is designed to handle. But I saw this other ticket that seemed very similar but for secrets. I wonder if we could do something like that? Only load metadata to list the pods and get the details on-demand?

To Reproduce
Steps to reproduce the behavior:

1. Open k9s
2. Navigate to the namespace with 13k pods
3. Wait about a minute
4. See pods
5. /<pod-name-filter>
6. Wait a couple of minutes
7. See a handful of pods I care about, if it is a small number k9s works fine again, if not there would still be latency

Expected behavior
K9s does not slow down.

Screenshots
It's my employer's cluster, doubt I could post a picture here. Let me know if there is something else I can provide.

Versions (please complete the following information):

• OS: macOS Big Sur
• K9s: v0.25.18
• K8s: v1.19.7

Additional context
The cluster is running on AWS EKS