Camel K (image)

registry-proxy.engineering.redhat.com/rh-osbs/integration-tech-preview-camel-k-rhel8-operator:1.0-28
registry-proxy.engineering.redhat.com/rh-osbs/integration-tech-preview-camel-k-rhel8-operator-metadata:integration-1.0-containers-candidate-98428-20200820030820

Manifests published to quay
Do we still need these?

Camel K (base image)

Component versions:
cxf : 3.3.6.fuse-jdk11-800021-redhat-00001
camel : 3.4.0.fuse-jdk11-800010-redhat-00001
camel-k-runtime : 1.4.1.fuse-jdk11-800003-redhat-00001
camel-quarkus : 1.0.0.CR3-fuse-jdk11-800001-redhat-00001
camel-k : 1.0.0.fuse-jdk11-800060-redhat-00001

Camel K Clients :

http://indy.psi.redhat.com/api/folo/track/build-59656/maven/hosted/build-59656/org/fuse/camel/k/linux-client/1.0.0.fuse-jdk11-800060-redhat-00001/linux-client-1.0.0.fuse-jdk11-800060-redhat-00001.tar.gz

http://indy.psi.redhat.com/api/folo/track/build-59656/maven/hosted/build-59656/org/fuse/camel/k/mac-client/1.0.0.fuse-jdk11-800060-redhat-00001/mac-client-1.0.0.fuse-jdk11-800060-redhat-00001.tar.gz

http://indy.psi.redhat.com/api/folo/track/build-59656/maven/hosted/build-59656/org/fuse/camel/k/windows-client/1.0.0.fuse-jdk11-800060-redhat-00001/windows-client-1.0.0.fuse-jdk11-800060-redhat-00001.tar.gz