You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default imagePullPolicy is Always for the lagoon-core chart.
Would it make sense to use IfNotPresent for releases, and leave Always for testing/local-dev only?
I want to use IfNotPresent so that restarting containers is quicker in a deployed production Lagoon, currently I need to modify all the services individually, as there isn't a way to set the policy override globally.
For example, there is an ability to provide a .imageTag that can be applied to most images that use the lagoon-core version. It would be nice to be able to have a .pullPolicy value that could be used for changing the imagePullPolicy on these same images.
The default imagePullPolicy is
Always
for the lagoon-core chart.Would it make sense to use
IfNotPresent
for releases, and leaveAlways
for testing/local-dev only?I want to use
IfNotPresent
so that restarting containers is quicker in a deployed production Lagoon, currently I need to modify all the services individually, as there isn't a way to set the policy override globally.For example, there is an ability to provide a
.imageTag
that can be applied to most images that use the lagoon-core version. It would be nice to be able to have a.pullPolicy
value that could be used for changing theimagePullPolicy
on these same images.The text was updated successfully, but these errors were encountered: