Camel-K Operator v1.6.8 Can Not Pull Image and Gets Stuck During Install or Upgrade

Solution Verified - Updated -

Issue

  • The camel-k-operator pod is stuck in a ImagePullBackOff or CrashLoopBackoff state
  • The camel-k-operator is generating alerts for CsvAbnormalOver30Min and KubeContainerWaiting because the operator pod is down
  • The camel-k-operator is having issues pulling the operator image:
Failed to pull image "registry.redhat.io/integration/camel-k-rhel8-operator@sha256:d4a49a873879d2e89ed2f4ea732cdc2cbddcf2ea2e5c136bcf1937797f7ae908": rpc error: code = Unknown desc = reading manifest sha256:d4a49a873879d2e89ed2f4ea732cdc2cbddcf2ea2e5c136bcf1937797f7ae908 in registry.redhat.io/integration/camel-k-rhel8-operator: unsupported: V2 schema 1 manifest digests are no longer supported for image pulls. Use the equivalent V2 schema 2 manifest digest instead. For more information see https://access.redhat.com/articles/6138332

Environment

  • Red Hat OpenShift Container Platform (OCP) 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content