Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-7172

kube-rbac-proxy container image is not getting pulled on DevWorkspace0.30 version

XMLWordPrintable

    • False
    • None
    • False
    • Workaround Exists
    • Hide

      A temporary workaround to get the pods running is to replace the kube-rbac-proxy container image in the devworkspace-operator CSV and the devworkspace-webhook-server deployment:

      1. Edit the DevWorkspace Operator CSV:

      $ oc edit csv devworkspace-operator.v0.30.0 -n openshift-operators

       
      and replace all references of

      registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:fde6314359436241171f6361f9a1e23c60bdf2d421c0c5740734d1dcf5f01ac2

      to

      registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:514e9e03f1d96046ff819798e54aa5672621c15805d61fb6137283f83f57a1e3

       
      2. Do the same procedure in step 1 for the devworkspace-webhook-server deployment and the devworkspace-controller-manager deployment

      $ oc edit deployment devworkspace-webhook-server -n openshift-operators
$ oc edit deployment devworkspace-controller-manager -n openshift-operators

       
      Eventually, the devworkspace-controller-manager and devworkspace-webhook-server pods will use the updated image:

      $ oc get pods -n openshift-operators
NAME READY STATUS RESTARTS AGE
devworkspace-controller-manager-54f7dd576b-2xx8k 2/2 Running 0 117s
devworkspace-webhook-server-579f68466f-c7vv2 2/2 Running 0 115s
devworkspace-webhook-server-579f68466f-fb8th 2/2 Running 0 95s

       

      Show
      A temporary workaround to get the pods running is to replace the kube-rbac-proxy container image in the devworkspace-operator CSV and the devworkspace-webhook-server deployment: 1. Edit the DevWorkspace Operator CSV: $ oc edit csv devworkspace- operator .v0.30.0 -n openshift-operators   and replace all references of registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:fde6314359436241171f6361f9a1e23c60bdf2d421c0c5740734d1dcf5f01ac2 to registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:514e9e03f1d96046ff819798e54aa5672621c15805d61fb6137283f83f57a1e3   2. Do the same procedure in step 1 for the devworkspace-webhook-server deployment and the devworkspace-controller-manager deployment $ oc edit deployment devworkspace-webhook-server -n openshift-operators $ oc edit deployment devworkspace-controller-manager -n openshift-operators   Eventually, the  devworkspace-controller-manager  and  devworkspace-webhook-server  pods will use the updated image: $ oc get pods -n openshift-operators NAME READY STATUS RESTARTS AGE devworkspace-controller-manager-54f7dd576b-2xx8k 2/2 Running 0 117s devworkspace-webhook-server-579f68466f-c7vv2 2/2 Running 0 115s devworkspace-webhook-server-579f68466f-fb8th 2/2 Running 0 95s  

      Description of problem:

      kube-rbac-proxy container image is not getting pulled on DevWorkspace0.30 version

      Prerequisites (if any, like setup, operators/versions):

      OCP 4.13+

      Latest available version of DevSpaces (3.14.0 or 3.15.0){}

      Steps to Reproduce

      Install OpenShift DevSpaces latest version (where the DevWorkSpace verison is 0.30) or If the DevSpaces latest version is already installed, the DevWorkspace would automatically upgrade from 0.29 to 0.30

      Actual results:

      All the pods related to DevWorkSpace should come up

      Expected results:

      Pods related to DevWorkSpace are going to ImagePullBackOffState

      Reproducibility (Always/Intermittent/Only Once): Always

      Acceptance criteria: 

       

      Definition of Done:

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

       

      $ oc get pods -n devspaces
NAME                                              READY   STATUS             RESTARTS        AGE
devspaces-operator-68cbd54b78-mdzcr               1/1     Running            0               12m
devworkspace-controller-manager-5558ff877-jrjhb   1/2     ImagePullBackOff   2 (7m47s ago)   12m
devworkspace-webhook-server-548db5cb6-2hbfl       1/2     ImagePullBackOff   0               12m
devworkspace-webhook-server-7b9b645654-5fh9l      1/2     ImagePullBackOff   0               10m
devworkspace-webhook-server-b79dd7db7-pbpcg       1/2     ImagePullBackOff   0               7m11s

       

       state:
      waiting:
        message: Back-off pulling image "registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:fde6314359436241171f6361f9a1e23c60bdf2d421c0c5740734d1dcf5f01ac2"
        reason: ImagePullBackOff
  - containerID: cri-o://2db6a00d6128f4dc7cc31e7af82f009bbf7575a2b851db6769ce44ed7b2a2f4e
    image: registry.redhat.io/devworkspace/devworkspace-rhel8-operator@sha256:e5a5d608efbeef9e0251e9138aa2b8c246683153344a7fab39dccdf59426dbaa
    imageID: registry.redhat.io/devworkspace/devworkspace-rhel8-operator@sha256:2422cd3f5645fa9334c00e211dbd495d74cf50ea716c6af68782295e18ab9f67
    lastState: {}

       

        1. image-2024-09-03-11-36-37-195.png
          image-2024-09-03-11-36-37-195.png
          95 kB

              aobuchow Andrew Obuchowicz
              rhn-support-disharma Diksha Sharma
              Votes:
              9 Vote for this issue
              Watchers:
              36 Start watching this issue

                Created:
                Updated:
                Resolved: