openshift / openshift/oadp-operator
OADP-732: Enable ability to use private registry for custom plugins (add image pull secrets)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 92
- Forks
- 93
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 43
Description
Is your feature request related to a problem? Please describe.
I want to use a custom plugins, the image of it is located on a private container registry.
It is not possible to add an imagePullSecret to the Velero deployment.
Describe the solution you'd like
Allow to set the imagePullSecrets property.
Describe alternatives you've considered
If the configuration of the imagePullSecrets property is not possible, it could be nice to indicate to the controller to ignore the modifications of this property, this one could be modified by a mutation at admission.
This is probably not the best idea, I'm not very inspired.
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 tracing how the operator configures the Velero deployment and where imagePullSecrets could be represented. Check the related custom resource configuration and deployment behavior for custom plugins using a private registry. Done means users can set imagePullSecrets and the resulting deployment can pull the plugin image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100