Adding pull policy specification to the MIC CRD

This policy will be used by the image puller pod. Currently image puller
pod uses IfNotPresent, which may create a discrepance with worker pod
whcih uses the pull policy of the KMM Module. So, image may be present
on the node, but not in repo, and in that case , image puller will be
successful, while worker will fail with pull policy Always

Author: yevgeny-shnaidman

api/v1beta1/moduleimagesconfig_types.go

@@ -67,6 +67,11 @@ type ModuleImagesConfigSpec struct {
 	// ImageRepoSecret contains pull secret for the image's repo, if needed
 	// +optional
 	ImageRepoSecret *v1.LocalObjectReference `json:"imageRepoSecret,omitempty"`
+
+	// +kubebuilder:default=IfNotPresent
+	// ImagePullPolicy defines the pull policy used for verifying the presence of the image
+	//+optional
+	ImagePullPolicy v1.PullPolicy `json:"imagePullPolicy"`
 }
 
 type ModuleImageState struct {

config/crd/bases/kmm.sigs.x-k8s.io_moduleimagesconfigs.yaml

@@ -44,6 +44,11 @@ spec:
               ModuleImagesConfigSpec describes the images of the Module whose status needs to be verified
               More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status
             properties:
+              imagePullPolicy:
+                default: IfNotPresent
+                description: ImagePullPolicy defines the pull policy used for verifying
+                  the presence of the image
+                type: string
               imageRepoSecret:
                 description: ImageRepoSecret contains pull secret for the image's
                   repo, if needed