Image pull-backoff for Plugin Registry when deploying Che via Operator

Describe the bug

When deploying the Che operator on OpenShift from the che-operator repo, the Che-Plugin-Registry container fails with an ImagePullBackOff error. Looking into the error further, it seems that the quay.io/eclipse/che-plugin-registry image doesn’t exist

Che version

Che 7 nightly Latest version of the operator from https://github.com/eclipse/che-operator/

Steps to reproduce

• Git clone https://github.com/eclipse/che-operator/
• Run deploy.sh
• Che-Plugin-Registry will error out with an ImagePullBackOff error:

     Warning  Failed     20s (x3 over 68s)  kubelet, 10.188.170.151  Failed to pull image
     "quay.io/eclipse/che-plugin-registry:nighlty": rpc error: code = Unknown desc = Error reading
     manifest nighlty in quay.io/eclipse/che-plugin-registry: manifest unknown: manifest unknown
  

There also seems to be a typo in the tag in quay.io/eclipse/che-plugin-registry:nighlty, which is causing the error. quay.io/eclipse/che-plugin-registry:nightly does exist.

Expected behavior

The Che operator deploys fine with the deploy.sh script

Runtime

• kubernetes (include output of kubectl version)
• Openshift (include output of oc version)
• minikube (include output of minikube version and kubectl version)
• minishift (include output of minishift version and oc version)
• docker-desktop + K8S (include output of docker version and kubectl version)
• other: (please specify)

johns-mbp-3:wtptestfix johncollier$ oc version
oc v3.11.0+0cbc58b
kubernetes v1.11.0+d4cacc0
features: Basic-Auth

Installation method

• chectl
• che-operator Latest from che-operator repo
• minishift-addon
• I don’t know

Additional context

[kushalg-1212]

can we open this again

Command server:deploy failed with the error: Failed to download image, reason: ImagePullBackOff, message: Back-off pulling image “quay.io/eclipse/che-plugin-registry:7.53.0”

deploying with minikube

che@CHE1:~$ chectl server:deploy --platform minikube Enable CLI usage data to be sent to Red Hat online services. More info: https://developers.redhat.com/article/tool-data-collection [y/n]: y › Current Kubernetes context: ‘minikube’ ✔ Verify Kubernetes API…[OK] ✔ 👀 Looking for an already existing Eclipse Che instance ✔ Verify if Eclipse Che is deployed into namespace “eclipse-che”…[Not Found] ↓ Check if OIDC Provider installed [skipped] → Dex will be automatically installed as OIDC Identity Provider ✔ ✈️ Minikube preflight checklist ✔ Verify if kubectl is installed ✔ Verify if minikube is installed ✔ Verify if minikube is running ↓ Start minikube [skipped] → Minikube is already running. ✔ Check Kubernetes version: [Found v1.24.3] ✔ Verify if minikube ingress addon is enabled ↓ Enable minikube ingress addon [skipped] → Ingress addon is already enabled. ✔ Retrieving minikube IP and domain for ingress URLs…[192.168.59.101.nip.io] ✔ Checking minikube version…[1.26.1] ✔ Following Eclipse Che logs ✔ Start following logs…[OK] ✔ Cert Manager v1.8.2 ✔ Install Cert Manager…[OK] ✔ Wait for Cert Manager…[OK] ✔ Create Namespace eclipse-che…[OK] ✔ Deploy Dex ✔ Create namespace: dex…[OK] ✔ Create issuer dex-selfsigned…[OK] ✔ Create certificate: dex-selfsigned…[OK] ✔ Create issuer dex…[OK] ✔ Create certificate: dex…[OK] ✔ Save Dex certificate…[OK: /tmp/dex-ca.crt] ✔ Add Dex certificate to Eclipse Che certificates bundle…[OK] ✔ Create Dex service account…[OK] ✔ Create Dex cluster role…[OK] ✔ Create Dex cluster role binding…[OK] ✔ Create Dex service…[OK] ✔ Create Dex ingress…[OK] ✔ Generate Dex username and password…[OK: admin:admin] ✔ Create Dex configmap…[OK] ✔ Create Dex deployment…[OK] ✔ Wait for Dex is ready…[OK] ✔ Configure API server ✔ Create /etc/ca-certificates directory…[OK] ✔ Copy Dex certificate into Minikube…[OK] ✔ Configure Minikube API server…[OK] ✔ Wait for Minikube API server…[OK] ✔ Deploy Eclipse Che ✔ Create ServiceAccount che-operator in namespace eclipse-che…[OK: created] ✔ Role and RoleBindings…[OK] ✔ Create Role che-operator…[OK: created] ✔ Create RoleBinding che-operator…[OK: created] ✔ Create ClusterRole che-operator…[OK: created] ✔ Create ClusterRoleBinding che-operator…[OK: created] ✔ Create Certificate che-operator-serving-cert…[OK: created] ✔ Create Issuer che-operator-selfsigned-issuer…[OK: created] ✔ Create Service che-operator-service…[OK: created] ✔ Create CRD checlusters.org.eclipse.che…[OK: created] ✔ Waiting 5 seconds for the new Kubernetes resources to get flushed…[OK] ✔ Create deployment che-operator in namespace eclipse-che…[OK: created] ✔ Operator pod bootstrap ✔ Scheduling…[OK] ✔ Downloading images…[OK] ✔ Starting…[OK] ✔ Create CheCluster Custom Resource…[Created] ❯ Post installation checklist ✔ PostgreSQL pod bootstrap ✔ Scheduling…[OK] ✔ Downloading images…[OK] ✔ Starting…[OK] ✔ Devfile Registry pod bootstrap ✔ Scheduling…[OK] ✔ Downloading images…[OK] ✔ Starting…[OK] ❯ Plug-in Registry pod bootstrap ✔ Scheduling…[OK] ✖ Downloading images → Failed to download image, reason: ImagePullBackOff, message: Back-off pulling image “quay.io/eclipse/che-plugin-registry:7.53.0”. Starting Eclipse Che Dashboard pod bootstrap Eclipse Che Gateway pod bootstrap Eclipse Che Server pod bootstrap Eclipse Che status check Create DevWorkspaceOperatorConfig Retrieving Che self-signed CA certificate Prepare post installation output Error: Command server:deploy failed with the error: Failed to download image, reason: ImagePullBackOff, message: Back-off pulling image “quay.io/eclipse/che-plugin-registry:7.53.0”. See details: /home/che/.cache/chectl/error.log. Eclipse Che logs: /tmp/chectl-logs/1662628585053.

[johnmcollier]

Opened https://github.com/eclipse/che-operator/pull/65