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 Docker images of the two sidecar containers (usage and output) in the workflow pod are always pulled even through the image is always the same (bitnami/kubectl:latest). Because of this, the pod and the containers remain in the ContainerCreating for a long time, even when the actual workflow jobs are being executed.
Because the image tag latest is used for the sidecar containers and no imagePullPolicy is specified in CalrissianJobTemplate.yaml, the image is always pulled.
Would it be possible to either allow configuring the image tag (to avoid using latest) or allow configuring the image pull policy for these two (identical) images?
The text was updated successfully, but these errors were encountered:
The Docker images of the two sidecar containers (usage and output) in the workflow pod are always pulled even through the image is always the same (
bitnami/kubectl:latest
). Because of this, the pod and the containers remain in theContainerCreating
for a long time, even when the actual workflow jobs are being executed.Because the image tag
latest
is used for the sidecar containers and noimagePullPolicy
is specified in CalrissianJobTemplate.yaml, the image is always pulled.Would it be possible to either allow configuring the image tag (to avoid using
latest
) or allow configuring the image pull policy for these two (identical) images?The text was updated successfully, but these errors were encountered: