spinframework / spinframework/spin-operator
Add imagePullSecrets support to Helm chart
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 289
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
The Spin Operator Helm chart currently doesn't provide an option to configure imagePullSecrets for the Spin Operator Deployment.
This causes issues when the operator image is hosted in a private registry, as users need to manually patch the Deployment after installation.
Proposed change
Add support in values.yaml:
imagePullSecrets:
- name: registry-secret
and propagate it to the operator Deployment:
spec:
template:
spec:
imagePullSecrets:
- name: registry-secret
This would allow users to configure private registry credentials directly through Helm.
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 with the Helm chart's values.yaml and the template for the operator Deployment. Add the configurable imagePullSecrets value and verify that Helm renders it under spec.template.spec.imagePullSecrets with the configured secret name.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100