Allow using existing ServiceAccount without creating a new one

Open Beginner friendly
#459 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
helm, kubernetes
Domain
devops

Research direction

Inspect templates/serviceaccount.yaml and templates/statefulset.yaml, then compare their behavior with the qdrant.serviceAccountName helper in templates/_helpers.tpl. Render the chart with serviceAccount.create set to false and an existing name, and verify that no ServiceAccount is created and the workload uses the specified name.

Written by the indexing model from the issue text.

Description

The qdrant Helm chart currently does not provide a way to use an existing ServiceAccount without creating a new one. The chart's _helpers.tpl template serviceAccountName already supports this pattern through values, but:

  1. The templates/serviceaccount.yaml template lacks a conditional guard and always creates a new ServiceAccount, regardless of serviceAccount.create setting.
  2. The templates/statefulset.yaml hardcodes serviceAccountName: {{ include "qdrant.fullname" . }} instead of calling the qdrant.serviceAccountName helper, making it impossible to use a pre-existing ServiceAccount.

Current Behavior

  1. serviceAccount.create: false + serviceAccount.name: existing-service acoount → Pod still tries to use auto-created SA; SCC/RBAC bindings for the existing SA are ignored
  2. Users deploying in restricted environments cannot reuse centrally-managed ServiceAccounts
  3. Duplicate ServiceAccount objects are created unnecessarily

Expected Behavior
When serviceAccount.create: false and serviceAccount.name is set:

  1. No ServiceAccount resource should be created
  2. Pod's serviceAccountName should use the specified existing SA
  3. Existing RBAC/SCC bindings for that SA should apply to the pod
Dominant language
Go
Stars
191
Forks
98
Avg merge
2d 4h
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from qdrant/qdrant-helm

All issues in qdrant/qdrant-helm

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.