tanishqgandhi1908 opened a new issue, #8972:
URL: https://github.com/apache/texera/issues/8972
### What happened?
The DaemonSet that pre-pulls the computing-unit image onto every node
hardcodes imagePullPolicy: Always. Every other template that pulls a Texera
image, including the Jupyter prepull DaemonSet, reads {{
.Values.texeraImages.pullPolicy }}.
So on clusters that load images into the nodes instead of pulling them from
a registry (kind, minikube, air-gapped installs), setting
texeraImages.pullPolicy to IfNotPresent or Never has no effect on this
DaemonSet. Its init container still tries to pull from the registry and fails
with ErrImagePull / ImagePullBackOff.
Expected: the prepuller follows texeraImages.pullPolicy, as the Jupyter
prepuller does.
Rendered with helm template on main:
```
pullPolicy=Always | CU prepuller: imagePullPolicy: Always | Jupyter
prepuller: imagePullPolicy: Always
pullPolicy=IfNotPresent | CU prepuller: imagePullPolicy: Always | Jupyter
prepuller: imagePullPolicy: IfNotPresent
pullPolicy=Never | CU prepuller: imagePullPolicy: Always | Jupyter
prepuller: imagePullPolicy: Never
```
### How to reproduce?
rom bin/k8s (after helm dependency build):
```
helm template t . --set texeraImages.pullPolicy=IfNotPresent \
--show-only
templates/base/workflow-computing-unit-pool/workflow-computing-unit-master-prepull-daemonset.yaml
\
| grep imagePullPolicy
```
It prints imagePullPolicy: Always.
### Version/Branch
1.4.0-incubating-SNAPSHOT (main)
### Commit Hash (Optional)
_No response_
### What browsers are you seeing the problem on?
_No response_
### Relevant log output
```shell
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
