This message was deleted.
# harvester
a
This message was deleted.
m
Nevermind. GPT4 helped me through the steps to patch the correct configuration🤣
👍 2
👀 1
b
(Correcting the configuration involves patching the prometheus object, not the statefulset directly) - there’s an existing (or several, I think) issue for this in github, and it’s scheduled to be fixed for 1.1.3 and 1.2 I believe
m
Is there a reason the limits on prom are so small, or that they are consistently below the needs of my cluster? Not sure whether everyone is having issues on the limits or just me. After I patched it I had to update it again to increase the limits
a
this issue is known, please refer https://github.com/harvester/harvester/issues/3839#issuecomment-1564405034 to fix it manually
@miniature-advantage-78722 we did not set the prometheus with way big amount of resources reservation by default, as some clusters are on limited resources. when your cluster have rich resources, set it to a big number is good