ArgoCD doesn't support helm k8s lookup and thus qdrant existing secret lookup fails
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 191
- Forks
- 98
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 6
Description
I just tried your latest changes with a ArgoCD deployment, by specifing a apiKeys via an existing secret like
apiKey:
valueFrom:
secretKeyRef:
name: "secretname"
key: "apikeyname"
This doesn't work, as ArgoCD doesn't support the helm lookup function:
https://github.com/argoproj/argo-cd/issues/5202
During debugging the issue I found out, that the qdrant helm chart tries to read the existing k8s secret and creates a new secret.
I'm looking for some alternative solution to specify the api keys outside the qdrant helm chart, so that I don't have to put the secerts as cleartext into our deployment repos... any suggestion?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the qdrant Helm chart's existing-secret lookup and the linked ArgoCD limitation around Helm lookup. Define an approach that lets api keys come from an external Kubernetes secret without placing secret values in deployment repositories, then verify that the chart renders and deploys correctly through ArgoCD.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100