Qdrant Helm tests fail: Entrypoint script requires writable $HOME but cluster enforces readOnlyRootFilesystem

Problem

The Helm tests for Qdrant fail because the entrypoint script attempts to write to $HOME/.curlrc, but the cluster enforces readOnlyRootFilesystem for all pods. The tests are currently disabled to unblock us.

Root Cause

The test script (entrypoint.sh) creates a .curlrc file at $HOME/.curlrc during startup. Since no pod runs with write permissions in this cluster, all filesystem locations except explicitly mounted emptyDir volumes are read-only.
The current workaround in values.yaml mounts an emptyDir at /root:

additionalVolumes:
  - name: tmp-home
    emptyDir: {}
additionalVolumeMounts:
  - name: tmp-home
    mountPath: /root

However, this doesn't solve the problem because:

• The test container runs as a non-root user, so $HOME is not /root

The Qdrant Helm chart does apply additionalVolumes and additionalVolumeMounts to the test pod, but there's currently no way to inject environment variables like HOME=/tmp into the test pod.

Expected Behavior

The Helm tests should pass successfully in a cluster that enforces readOnlyRootFilesystem on all pods.

Start with the Helm test pod templates and values.yaml, then inspect the test entrypoint.sh that writes to $HOME/.curlrc. Check how the test container receives environment variables and mounted volumes, and verify the disabled Helm tests pass with readOnlyRootFilesystem enforced.