Support for Extra Volumes and Volume Mounts
Open
Nobody has claimed this yet.
Feature
Triage-Needed
- Dominant language
- Go
- Stars
- 88
- Forks
- 66
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
Feature Request: Support for Extra Volumes and Volume Mounts
Similar to the AWX operator, add support for:
api.extra_volumes/api.extra_volume_mountsworker.extra_volumes/worker.extra_volume_mountscontent.extra_volumes/content.extra_volume_mounts
Use Case: Integration with Azure Key Vault CSI Driver via SecretProviderClass
Example:
spec:
api:
extra_volumes: |
- name: secrets-store
csi:
driver: secrets-store.csi.k8s.io
readOnly: true
volumeAttributes:
secretProviderClass: "my-secrets"
extra_volume_mounts: |
- name: secrets-store
mountPath: "/mnt/secrets"
readOnly: true
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 locating how the operator represents and applies the api, worker, and content settings, then trace where their pod volumes and mounts are generated. Use the SecretProviderClass and CSI volume example as the target input. Done means all three components accept extra_volumes and extra_volume_mounts and render them into their workloads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100