Configurable pull policy when `velero install`
kaovilai opened this issue ยท 2 comments
kaovilai commented
Describe the problem/challenge you have
I would like pull policy to be configurable with velero install
velero/pkg/install/deployment.go
Lines 232 to 236 in 6588141
Describe the solution you'd like
Anything else you would like to add:
Environment:
- Velero version (use
velero version
): - Kubernetes version (use
kubectl version
): - Kubernetes installer & version:
- Cloud provider or hardware configuration:
- OS (e.g. from
/etc/os-release
):
Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
- ๐ for "The project would be better with this feature added"
- ๐ for "This feature will not enhance the project in a meaningful way"
kaovilai commented
Scenario is I build and run a dev image reusing tag. The tag is not latest, so I need to use pullAlways for changes to affect.