influxdb: what are the minimum CPU/Memory limits/requests?

I am installing influxdb into my k3s single-node instance. I have this in my values.yaml, copied from the default values:

```
resources:
requests:
memory: 256Mi
cpu: 0.1
limits:
memory: 256Mi
cpu: 0.1
```

But as soon as I add any limits, the pod never gets to a healthy/ready state. The pod logs only contain this:

```
ts=2023-10-06T07:01:20.070536Z lvl=info msg="InfluxDB starting" log_id=0khxVIHW000 version=1.8.10 branch=1.8 commit=688e697c51fd
ts=2023-10-06T07:01:20.070606Z lvl=info msg="Go runtime" log_id=0khxVIHW000 version=go1.13.8 maxprocs=4
```

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... :-)

Start with the chart's values.yaml and reproduce the InfluxDB pod startup using the reported CPU and memory requests and limits. Compare the readiness behavior and startup logs with the larger limits that succeed; done means identifying the minimum supported resources or documenting how the chart configuration should be adjusted.

Written by the indexing model from the issue text.