Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-5990

[release-5.6] Update kube-rbac-proxy to continue support for arm64/ppc64le arch cluster

XMLWordPrintable

    • False
    • None
    • False
    • NEW
    • NEW
    • Log Storage - Sprint 258

      Description of problem:

      Loki operator is failing to deploy on arm64 cluster. Controller manager is in CrashLoop status.

      Error:

      Failed to pull image "registry.redhat.io/openshift4/ose-kube-rbac-proxy@sha256:dc319a431162ad219ea3b3efdea1913b7342ae6c648266e0854b2e4844c4b9fb": choosing image instance: no image found in manifest list for architecture arm64, variant "v8", OS linux
      $ oc get csv -n openshift-operators-redhat
      NAME                   DISPLAY         VERSION   REPLACES   PHASE
      loki-operator.v6.0.0   Loki Operator   6.0.0                Installing
      
      $ oc get pods -n openshift-operators-redhat
      NAME                                                READY   STATUS         RESTARTS   AGE
      loki-operator-controller-manager-6d4f8f7596-8mj8p   1/2     ErrImagePull   0          2m2s
      

      Version-Release number of selected component (if applicable): Logging 6.0 (openshift-logging-6.0.0-20240820.2)

      How reproducible: Always

      Steps to Reproduce:

      1. Deploy Loki on arm64 cluster

      Actual results:

      Loki Operator deployment is failing

      Expected results:

      Loki Operator should be successfully deployed.

      Additional info:

      In 5.6 kube-rbac-proxy is also used by the Elasticsearch Operator.

              rojacob@redhat.com Robert Jacob
              rhn-support-kbharti Kabir Bharti
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: