This message was deleted.
# k3s
a
This message was deleted.
c
that’s not the correct fix.
getting “no metrics to serve” is normal for a minute or two after the pod comes up, when it hasn’t scraped the nodes yet. It should not continue after that. Note that the metrics are not persisted across pod restarts - they’re only stored in memory. So it’s normal to see that error every time the pod restarts.
c
I waited for few days before I made the change and there was no metrics. Once the change is made i see metrics within few minutes. I am using k3s version v1.30.5+k3s1
c
that flag really isn’t going to make a difference. I would probably add --debug and see why it’s failing to scrape, and then resolve that.