-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
1. Proposed title of this feature request
Add Toleration Support Kubernetes Image Puller Operator
2. What is the nature and description of the request?
Add Toleration Support Kubernetes Image Puller Operator
Currently there is no CRD Spec to define a Toleration for nodes that are tainted on the Kubernetes Image Puller Operator.
apiVersion: che.eclipse.org/v1alpha1 kind: KubernetesImagePuller metadata: name: kubernetes-imagepuller-operator namespace: openshift-imagepuller-operator labels: argocd.argoproj.io/instance: openshift-imagepuller-operator spec: configMapName: k8s-image-puller cachingCPURequest: 5m daemonsetName: k8s-image-puller cachingIntervalHours: '2' imagePullerImage: 'quay.io/eclipse/kubernetes-image-puller:next' cachingMemoryRequest: 8Mi deploymentName: kubernetes-image-puller cachingCPULimit: 10m images: '' cachingMemoryLimit: 32Mi status: imagePullerImage: 'quay.io/eclipse/kubernetes-image-puller:next'
3. Why does the customer need this? (List the business requirements here)
So they could use this on tainted nodes such as infra and gpu nodes.
Additionally, this feature is already supported by the upstream.
4. List any affected packages or components.
Kubernetes Image Puller Operator
