Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-13261

Can't install camel-k operator from private registry on testing env

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • fuse-next-TP1-GA
    • Camel-K
    • None

      I am installing camel-k operator from private registry on quay.io.

      oc get secret quay                                          
      NAME   TYPE                             DATA   AGE
      quay   kubernetes.io/dockerconfigjson   1      47s
      
       oc secrets link default quay --for=pull
      
      kamel install --olm=false --operator-image=quay.io/rh_integration/camel-k:fuse-8.0-openshift-rhel-8-containers-candidate-61687-20200325032831
      Camel K installed in namespace test 
      
      oc get pods
      NAME                                READY   STATUS             RESTARTS   AGE
      camel-k-operator-7d867dc587-z67ft   0/1     ImagePullBackOff   0          18s
      
       oc get deployment camel-k-operator -o yaml | grep image
              image: quay.io/rh_integration/camel-k:fuse-8.0-openshift-rhel-8-containers-candidate-61687-20200325032831
              imagePullPolicy: IfNotPresent
      
      

      Operator deployment is running with camel-k-operator service account.

      Workaround:

      oc get deployment camel-k-operator -o yaml | grep serviceAccount
            serviceAccount: camel-k-operator
            serviceAccountName: camel-k-operator
      
      oc secrets link camel-k-operator quay --for=pull
      
      oc delete pods --all  
      pod "camel-k-operator-7d867dc587-z67ft" deleted
      
      oc get pods         
      NAME                                READY   STATUS    RESTARTS   AGE
      camel-k-operator-7d867dc587-42tz4   1/1     Running   0          22s
      
      

            nicolaferraro Nicola Ferraro (Inactive)
            jbouska@redhat.com Jan Bouska
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: