Pod not starting: Cannot ping influxd server

Hi,

I'm currently trying to get the helm chart running but it seems to be stuck at startup as it can't seem to ping the influxd server as the logs below illustrate. Any help would be appreciated.

My general setup is as follows:
- K3s Cluster with 2 Raspis
- Standard chart values except providing the storageClass name for my nfs provisioner
- NFS permissions do not get squashed
- Folders seem to have correct UID/GID of 1000:1000

```
Command "print-config" is deprecated, use the influx-cli command server-config to display the configuration values from the running server
Command "print-config" is deprecated, use the influx-cli command server-config to display the configuration values from the running server
Command "print-config" is deprecated, use the influx-cli command server-config to display the configuration values from the running server
Command "print-config" is deprecated, use the influx-cli command server-config to display the configuration values from the running server
Command "print-config" is deprecated, use the influx-cli command server-config to display the configuration values from the running server
Command "print-config" is deprecated, use the influx-cli command server-config to display the configuration values from the running server
2023-11-01T21:35:40. info booting influxd server in the background {"system": "docker"}
ts=2023-11-01T21:35:40.540076Z lvl=info msg="Welcome to InfluxDB" log_id=0lFCrazl000 version=v2.3.0+SNAPSHOT.090f681737 commit=090f681737 build_date=2022-06-16T19:34:04Z
ts=2023-11-01T21:35:40.540350Z lvl=warn msg="nats-port argument is deprecated and unused" log_id=0lFCrazl000
2023-11-01T21:35:41. info pinging influxd... {"system": "docker", "ping_attempt": "0"}
2023-11-01T21:35:42. info pinging influxd... {"system": "docker", "ping_attempt": "1"}
2023-11-01T21:35:43. info pinging influxd... {"system": "docker", "ping_attempt": "2"}
2023-11-01T21:35:44. info pinging influxd... {"system": "docker", "ping_attempt": "3"}
2023-11-01T21:35:45. info pinging influxd... {"system": "docker", "ping_attempt": "4"}
2023-11-01T21:35:46. info pinging influxd... {"system": "docker", "ping_attempt": "5"}
2023-11-01T21:35:47. info pinging influxd... {"system": "docker", "ping_attempt": "6"}
2023-11-01T21:35:48. info pinging influxd... {"system": "docker", "ping_attempt": "7"}
2023-11-01T21:35:49. info pinging influxd... {"system": "docker", "ping_attempt": "8"}
2023-11-01T21:35:50. info pinging influxd... {"system": "docker", "ping_attempt": "9"}
2023-11-01T21:35:51. info pinging influxd... {"system": "docker", "ping_attempt": "10"}
2023-11-01T21:35:52. info pinging influxd... {"system": "docker", "ping_attempt": "11"}
2023-11-01T21:35:53. info pinging influxd... {"system": "docker", "ping_attempt": "12"}
2023-11-01T21:35:54. info pinging influxd... {"system": "docker", "ping_attempt": "13"}
2023-11-01T21:35:55. info pinging influxd... {"system": "docker", "ping_attempt": "14"}
2023-11-01T21:35:56. info pinging influxd... {"system": "docker", "ping_attempt": "15"}
2023-11-01T21:35:57. info pinging influxd... {"system": "docker", "ping_attempt": "16"}
2023-11-01T21:35:58. info pinging influxd... {"system": "docker", "ping_attempt": "17"}
2023-11-01T21:35:59. info pinging influxd... {"system": "docker", "ping_attempt": "18"}
2023-11-01T21:36:00. info pinging influxd... {"system": "docker", "ping_attempt": "19"}
2023-11-01T21:36:01. info pinging influxd... {"system": "docker", "ping_attempt": "20"}
2023-11-01T21:36:02. info pinging influxd... {"system": "docker", "ping_attempt": "21"}
2023-11-01T21:36:03. info pinging influxd... {"system": "docker", "ping_attempt": "22"}
2023-11-01T21:36:05. info pinging influxd... {"system": "docker", "ping_attempt": "23"}
2023-11-01T21:36:06. info pinging influxd... {"system": "docker", "ping_attempt": "24"}
2023-11-01T21:36:07. info pinging influxd... {"system": "docker", "ping_attempt": "25"}
2023-11-01T21:36:08. info pinging influxd... {"system": "docker", "ping_attempt": "26"}
2023-11-01T21:36:09. warn cleaning bolt and engine files to prevent conflicts on retry {"system": "docker", "bolt_path": "/var/lib/influxdb2/influxd.bolt", "engine_path": "/var/lib/influxdb2"}
```

Start with the Helm chart values and the pod logs shown in the issue, then inspect how the chart configures the InfluxDB server and its persistent storage on Kubernetes. Reproduce the startup failure and determine what prevents the pod from completing its InfluxDB ping; done means the pod starts successfully with the stated storageClass and the ping loop no longer retries.

Written by the indexing model from the issue text.