Do not fail if imagePuller CRD does not exist

[sleshchenko]

What does this PR do?

Do not fail if imagePuller CRD does not exist.

I did the minimal changes which should fix the issue but that logic in general it seems complex and may have other bugs.

What issues does this PR fix or reference?

It fixes eclipse-che/che#19207 on my RHPDS instance.

How to test this PR?

I tested only deploying Che with imagePuller disabled, before it failed with

"Error uninstalling Image Puller: no matches for kind \"KubernetesImagePuller\" in version \"che.eclipse.org/v1alpha1\""

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix
• Custom resource definition file is up to date
• Nightly OLM bundle is up to date
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

[codecov]

Codecov Report

Merging #700 (4db0d07) into master (d2e4ba9) will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           master     #700   +/-   ##
=======================================
  Coverage   32.68%   32.69%           
=======================================
  Files          50       50           
  Lines        5452     5451    -1     
=======================================
  Hits         1782     1782           
+ Misses       3402     3401    -1     
  Partials      268      268           

Impacted Files	Coverage Δ
pkg/deploy/kubernetes_image_puller.go	0.00% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d2e4ba9...4db0d07. Read the comment docs.

[sleshchenko]

@tolusha fixes LGTM )

[metlos]

Note that I've seen this on OpenShift 4.4.6, 4.6 and 4.7. On clusters where this was not happening, it started happening for me after 5-10 rescalings of the che-operator. I did the rescaling (to 0 and back to 1) to restart the operator and force a reconcile while debugging my wip changes.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AndrienkoAleksandr, sleshchenko, tolusha
To complete the pull request process, please assign after the PR has been reviewed.
You can assign the PR to them by writing /assign in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[AndrienkoAleksandr]

/test v7-che-operator-single-host-nightly-deployment

[AndrienkoAleksandr]

/test v6-che-operator-olm-nightly-deployment

[openshift-ci-robot]

New changes are detected. LGTM label has been removed.