Kubernetes service widget: Pod selector set to empty string not selecting all the pods in the namespace

[swooshant]

Description

I have the entry below and it does not get the correct stats for all the pods in the namespace. I'm not sure if I'm missing something to make sure that this is working. I tried including pod selectors but that didn't work either (see second config below). I made sure that all the pods have the app.kubernetes.io/instance: cert-manager label and they do. When I do a kubectl top -n cert-manager pods and then add up the memory results, it doesn't equal what the widget shows. Looks like the widget is only targeting app.kubernetes.io/name: cert-manager pods even though I'm using a pod selector.

Config 1

- Cert Manager [Cloud]:
icon: https://raw.githubusercontent.com/cert-manager/cert-manager/1035bb44ca8e9a1cd49c9de79dd5b28af1dcc972/logo/logo.svg
description: Kubernetes TLS automatic certificate manager
namespace: cert-manager
app: cert-manager
showStats: true
pod-selector: ""

Config 2 - With pod selector set

- Cert Manager [Cloud]:
icon: https://raw.githubusercontent.com/cert-manager/cert-manager/1035bb44ca8e9a1cd49c9de79dd5b28af1dcc972/logo/logo.svg
description: Kubernetes TLS automatic certificate manager
namespace: cert-manager
app: cert-manager
showStats: true
pod-selector: >-
app.kubernetes.io/instance in (
cert-manager
)

homepage version

v0.8.13

Installation method

Other (please describe above)

Configuration

Kubernetes install

Container Logs

No response

Browser Logs

No response

Troubleshooting

I switched the pod selector between the two configs as mentioned in the description. I tried this for another namespace/service like longhorn and it didn't work. Looks like the "app: cert-manager" entry is taking over and only pods with this label app.kubernetes.io/name: cert-manager are working.

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

Based on the information provided and the context from the sources, it seems that the issue you're experiencing is related to the way the pod-selector is being used in your configuration. When you set pod-selector: "", it is supposed to select all pods in the namespace, but it appears that it's not functioning as expected in your case.

From the sources, it's clear that the pod-selector should be able to override the default behavior, which is to use app.kubernetes.io/name as the label selector. Since you've tried using a specific pod selector with app.kubernetes.io/instance in (cert-manager) and it's still not showing the correct stats, there might be an issue with how the Homepage application is interpreting the pod-selector field.

One thing to note from the sources is that there was a documentation error where podSelector was suggested instead of pod-selector. Make sure you are using pod-selector in your configuration as per the corrected documentation.

If you've confirmed that the label app.kubernetes.io/instance: cert-manager is correctly applied to all relevant pods and the issue persists, this might be a bug with the Homepage application. In such a case, it would be advisable to report this issue to the maintainers of the Homepage application, providing them with the details of your configuration and the behavior you're observing.

You can report the issue on the Homepage GitHub repository's issues section, which is a common practice for reporting bugs and requesting features or support.

This comment was generated by Glime.

[swooshant]

Yup confirmed they all have "app.kubernetes.io/instance": "cert-manager" but different "app.kubernetes.io/name: <>" values. I'm using a kubernetes config map to write out the file as given in the homepage kubernetes installation/configuration instructions