Allow to change k8s imagePullPolicy

Is your feature request related to a problem? Please describe. With cloudflow 2.0.22 it is not possible to configure the imagePullPolicy for images when deploying to k8s. This makes it difficult/impossible to use some options for pushing/pulling images with minikube, see https://minikube.sigs.k8s.io/docs/handbook/pushing/ Most of the mentioned options requires a imagePullPolicy which is different from Always (which is what cloudflow uses per default)

Is your feature request related to a specific runtime of cloudflow or applicable for all runtimes? Applicable to all runtimes. As its a k8s deployment limitation.

Describe the solution you’d like I dont have a good solution in mind right now. All I can think of is extending the existing k8s configuration settings by adding the imagePullPolicy as another possible setting. eg:

cloudflow.streamlets.valid-logger.kubernetes.pods.pod.containers.container.imagePullPolicy = "Never"

Describe alternatives you’ve considered The only two alternatives I can think of are:

1. Using a dedicated image registry with minikube. Which is more effort than the handy minikube cache I typically use.
2. Updating/patching the streamlet k8s Deployment and changing the imagePullPolicyafter it was deployed. Quite an ugly solution.

Additional context None

[leozilla]

@andreaTP yeah sure I can add something to the docs

[andreaTP]

Thanks a lot for wrapping it up all together @leozilla ! Yes that’s more or less how I got it working on microk8s as well. We might want to improve the experience in the future, but, as of today, this is it, if you want/can add a section with those steps to the docs it will be great 🙂 .

A quick note on:

kubectl config set-context --current --namespace="" # this is necessary to work around a current bug in 2.0.22

This is fixed and new binaries are published, just re-download the CLI.