-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow option to specify image pull policy for component container image #4494
Comments
Related to: devfile/api#89 |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
/remove-lifecycle rotten Since there's already an issue about this on devfile side, I'm setting |
recently released odo v3.6 added support for Demo can be found in release notes https://odo.dev/blog/odo-v3.6.0/#extend-pod-and-container-specification-with-devfile-attributes-pod-overrides-and-container-overrides adding the following lines to attributes:
container-overrides:
imagePullPolicy: IfNotPresent /close |
@kadel: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/kind feature
Which functionality do you think we should add?
Odo should allow users to specify an image pull policy for a component's container image.
Why is this needed?
Using local images for components is particularly necessary when testing out stack image changes. Without being able to change the image pull policy, a local image cannot be used.
The text was updated successfully, but these errors were encountered: