Replies: 2 comments
-
i have the same issue, it started after upgrading from k3s 1.29.x to 1.30.x, problem still persist after upgrading to 1.31.4 metrics-server is running fine and kubectl top pods | nodes is working as well. message is written in journal log 5 - 6 times per minute causing higher load on k3s-server.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
created a new thread #11526 as this one is closed. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
My logs are full of
477 metrics.go:299] "Failed to get storage metrics" storage_cluster_id="etcd-0" err="context deadline exceeded"
I run a K3s cluster version 1.31.2 with kine.
it seems to be generated by the Apiserver ?
Happy to provide more infos if needed
Beta Was this translation helpful? Give feedback.
All reactions