-
Bug
-
Resolution: Done
-
Major
-
fuse-7.3
-
None
➜ camel-k ./kamel version Camel K Client 1.0.0.fuse-730029 ➜ camel-k ./kamel install ➜ camel-k oc describe deployment camel-k-operator Name: camel-k-operator Namespace: myproject CreationTimestamp: Wed, 17 Apr 2019 09:30:50 +0200 Labels: app=camel-k camel.apache.org/component=operator Annotations: deployment.kubernetes.io/revision=1 Selector: name=camel-k-operator Replicas: 1 desired | 1 updated | 1 total | 0 available | 1 unavailable StrategyType: Recreate MinReadySeconds: 0 Pod Template: Labels: camel.apache.org/component=operator name=camel-k-operator Service Account: camel-k-operator Containers: camel-k-operator: Image: docker.io/apache/camel-k:1.0.0.fuse-730029 Port: <none> Command: camel-k Environment: WATCH_NAMESPACE: (v1:metadata.namespace) OPERATOR_NAME: camel-k POD_NAME: (v1:metadata.name) Mounts: <none> Volumes: <none> Conditions: Type Status Reason ---- ------ ------ Available False MinimumReplicasUnavailable Progressing True ReplicaSetUpdated OldReplicaSets: <none> NewReplicaSet: camel-k-operator-7bf7965c9f (1/1 replicas created) Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal ScalingReplicaSet 30s deployment-controller Scaled up replica set camel-k-operator-7bf7965c9f to 1
We should use productized image from registry.redhat.io/fuse7 repository instead of docker.io/apache/camel-k:1.0.0.fuse-730029.