Integrations can't be build when using Camel K as runtime due to misaligned components.

Integration platform output:

{{ apiVersion: camel.apache.org/v1alpha1
kind: IntegrationPlatform
metadata:
creationTimestamp: 2020-07-02T05:59:48Z
generation: 3
labels:
app: camel-k
owner: 366d6321-bf2b-4d4e-aacc-6b70854f57a4
name: camel-k
namespace: mmuzikar
ownerReferences:

• apiVersion: syndesis.io/v1beta1
  blockOwnerDeletion: true
  controller: true
  kind: Syndesis
  name: app
  uid: 366d6321-bf2b-4d4e-aacc-6b70854f57a4
  resourceVersion: "308784"
  selfLink: /apis/camel.apache.org/v1alpha1/namespaces/mmuzikar/integrationplatforms/camel-k
  uid: 60847179-feb1-4e70-95ca-dafc222a8116
  spec:
  build:
  baseImage: quay.io/rh_integration/fuse-camel-k-rhel7-operator:1.7-6
  buildStrategy: routine
  camelVersion: 2.23.2.fuse-770007-redhat-00001
  localRepository: /tmp/artifacts/m2
  maven:
  settings:
  configMapKeyRef:
  key: settings.xml
  name: camel-k-maven-settings
  persistentVolumeClaim: camel-k
  publishStrategy: S2I
  registry: {}
  runtimeVersion: 0.3.4.fuse-770006-redhat-00001
  timeout: 5m0s
  cluster: OpenShift
  profile: OpenShift
  resources: {}
  status:
  phase: Ready}}

Integration output:
{{apiVersion: camel.apache.org/v1alpha1
kind: Integration
metadata:
annotations:
prometheus.io/port: "9779"
prometheus.io/scrape: "true"
syndesis.io/deploy-id: i-MBDAjbmjsYd0XYKS9riz:1
syndesis.io/deployment-version: "1"
syndesis.io/integration-id: i-MBDAjbmjsYd0XYKS9riz
syndesis.io/integration-name: CamelK DB to log
creationTimestamp: 2020-07-02T06:20:22Z
generation: 1
labels:
syndesis.io/app: syndesis
syndesis.io/component: integration
syndesis.io/deployment-version: "1"
syndesis.io/integration: CamelK-DB-to-log
syndesis.io/integration-id: i-MBDAjbmjsYd0XYKS9riz
syndesis.io/type: integration
syndesis.io/username: developer
name: i-camelk-db-to-log
namespace: mmuzikar
resourceVersion: "309222"
selfLink: /apis/camel.apache.org/v1alpha1/namespaces/mmuzikar/integrations/i-camelk-db-to-log
uid: d9ca148c-7478-4e1b-8e0c-0fb882303aed
spec:
configuration:

• type: property
  value: customizer.metadata.enabled=true
• type: property
  value: customizer.tracing.enabled=true
• type: property
  value: customizer.syndesis.enabled=true
• type: env
  value: AB_JMX_EXPORTER_CONFIG=/etc/camel/resources/prometheus-config.yml
• type: property
  value: camel.context.streamCaching=true
• type: secret
  value: i-camelk-db-to-log
• type: property
  value: customizer.tracing.serviceName=i-MBDAjbmjsYd0XYKS9riz
• type: env
  value: JAEGER_ENDPOINT=http://syndesis-jaeger-collector:14268/api/traces
• type: env
  value: JAEGER_TAGS=integration.version=1
• type: env
  value: JAEGER_SAMPLER_TYPE=const
• type: env
  value: JAEGER_SAMPLER_PARAM=1
  dependencies:
• mvn:org.apache.camel:camel-mustache
• bom:io.syndesis.integration/integration-bom-camel-k/pom/1.10.0.fuse-770014-redhat-00001
• mvn:io.syndesis.integration/integration-runtime-camelk
• mvn:io.syndesis.connector/connector-sql
  repositories: []
  resources:
• contentKey: prometheus-config.yml
  contentRef: syndesis-prometheus-agent-config
  mountPath: /etc/camel/resources
  name: prometheus-config.yml
  type: data
• compression: false
  content: '...'
  name: mapping-flow-0-step-3.json
  type: data
  sources:
• compression: false
  content: '...'
  language: syndesis
  name: i-mbdajbmjsyd0xyks9riz
  traits:
  camel:
  configuration:
  runtime-version: 0.3.4.fuse-770008-redhat-00001
  version: 2.23.2.fuse-770009-redhat-00001
  jolokia:
  configuration:
  enabled: "true"
  port: "8778"
  owner:
  configuration:
  target-annotations: prometheus.io/port,prometheus.io/scrape
  target-labels: syndesis.io/component,syndesis.io/integration-id,syndesis.io/deployment-version,syndesis.io/username,syndesis.io/integration,syndesis.io/type,syndesis.io/app
  prometheus:
  configuration:
  enabled: "true"
  port: "9779"
  service-monitor: "false"}}

And camel-catalog-2.23.2.fuse-770007-redhat-00001 is the productized catalog imported by the Camel K operator so a respin of Camel K is needed?