You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
We have installed koordinator using helm chart mentioned in the documentation https://koordinator.sh/docs/installation/ and we are getting continously crashloopbackoff for koordlet. Although I have already raised this issue in issue #2028 and here provided solution was to check node space , so my issue got resolved for most of the pods but we are still getting this error even after node has enough space.
kubectl get po -n koordinator-system |grep -v Running
NAME READY STATUS RESTARTS AGE
koordlet-hx5gh 0/1 CrashLoopBackOff 309 (2m54s ago) 2d23h
What you expected to happen:
All pods should run properly without error. How to reproduce it (as minimally and precisely as possible):
You can use the values.yaml mentioned above and reproduce this issue. Anything else we need to know?:
hi @kavita1205, as mentioned in #2028, please check if the memory/RAM space is enough since instead of the disk, the koordlet mounted the metrics store via the tmpfs by default. For more info, please check the koordlet Daemonset template. For a workaround, you can change the chart variable koordlet.hostDirs.koordletTSDBDir to a hostPath to mount disk space if needed.
What happened:
We have installed koordinator using helm chart mentioned in the documentation https://koordinator.sh/docs/installation/ and we are getting continously crashloopbackoff for koordlet. Although I have already raised this issue in issue #2028 and here provided solution was to check node space , so my issue got resolved for most of the pods but we are still getting this error even after node has enough space.
Error message:
Node space:
below is the values.yaml
What you expected to happen:
All pods should run properly without error.
How to reproduce it (as minimally and precisely as possible):
You can use the values.yaml mentioned above and reproduce this issue.
Anything else we need to know?:
Environment:
kubectl version
): 1.24The text was updated successfully, but these errors were encountered: