Generating apiKey

[apocalypsation1]

Followed your values.yaml chart regarding on apiKey.
I want to create my own api key instead of qdrant generating it.
But when i run together with the helm installl. qdrant will generate one qdrant-vector-apikey and my test-qdrant in secret.
And the statefulset will be using qdrant-vector-apikey instead of test-qdrant.

apiKey:
  valueFrom:
    secretKeyRef:
      name: test-qdrant
      key: qdrant-key

Problem with the use of lookup() function in the helm chart's helpers.tpl file, i don't have a running kubernetes cluster to query the secret from.

{{- $secretObj := (lookup "v1" "Secret" .Release.Namespace (printf "%s-apikey" (include "qdrant.fullname" . ))) | default dict -}}

[vermut]

Helm lookups play extremely bad with ArgoCD. I would be very nice to avoid that and use kubernetes secret volume mounts instead.

[jneuff]

I also wanted to bring my own apiKey. Just stumbled upon the lookup. Ideally, qdrant would be referencing the user provided secret directly at runtime.

[jneuff]

The biggest hurdle to get there is that the secret containing the apiKey is currently expected to be in some predefined qdrant config format: https://github.com/qdrant/qdrant-helm/blob/main/charts/qdrant/templates/statefulset.yaml#L195
It would be simpler, if the secret would be mounted with key projection of the apiKey.

[mrbnd]

workaround

values:
  # 1. Disable built-in key generation to prevent the chart from creating secrets
  apiKey: false
  readOnlyApiKey: false

  # 2. Inject the API Key manually via environment variables.
  # Qdrant automatically enables authentication when QDRANT__SERVICE__API_KEY is set.
  env:
    - name: QDRANT__SERVICE__API_KEY
      valueFrom:
        secretKeyRef:
          name: qdrant-secrets # The name of your manual Kubernetes Secret
          key: apiKey          # The key inside the secret containing the actual