Pods started by CDAP such as system app pods and preview runner pods should have a way to configure imagePullPolicy.
Description
Release Notes
Pods created by CDAP now inherit their ImagePullPolicy from the pod which created them.
Activity
Show:
Dennis Li July 16, 2021 at 5:02 PM
Done, thanks!
Amit Virmani July 16, 2021 at 5:38 AM
- can we resolve this?
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Reporter
Sagar Kapare
Sagar KapareLabels
Affects versions
Components
Fix versions
Priority
Major
Created July 1, 2021 at 5:50 PM
Updated August 24, 2021 at 5:57 PM
Resolved July 16, 2021 at 6:03 AM
If the Kubernetes environment where CDAP is installed does not have access to the internet, typically user would load the required docker images locally to all nodes and refer to those images in the CDAP CR. User would also set the imagePullPolicy to Never, so that docker image is looked into the local repository only.
In this set up if the image is tagged with ":latest" tag, CDAP system services pods (app-fabric, logs etc.) starts fine. However pods for preview runners, pipeline studio, wrangler, delta service failed to start. These pods are created by CDAP data plane and it seems like imagePullPolicy is not propagated to them causing them always to fetch ":latest" image from internet.