Seems like using 1CPU and 1Gi of RAM allows the pod to start. Which is too much for my use case, where there should hardly be much work for the pod to do. I noticed it uses about 20Mi of RAM while running...
It looks like the process tries to allocate memory or CPU and fails, if the limits are too small. Can this be tweaked somehow?
I would prepare a PR to update the chart's values.yaml with proper values, as soon as someone confirms it really needs 1Gi of RAM or 1 CPU to start... :-)
I am installing influxdb into my k3s single-node instance. I have this in my values.yaml, copied from the default values:
But as soon as I add any limits, the pod never gets to a healthy/ready state. The pod logs only contain this:
Seems like using 1CPU and 1Gi of RAM allows the pod to start. Which is too much for my use case, where there should hardly be much work for the pod to do. I noticed it uses about 20Mi of RAM while running...
It looks like the process tries to allocate memory or CPU and fails, if the limits are too small. Can this be tweaked somehow?
I would prepare a PR to update the chart's values.yaml with proper values, as soon as someone confirms it really needs 1Gi of RAM or 1 CPU to start... :-)