Building a first HyperSync integration

How a Camel route saved in Kaoto is scheduled as a HyperSync CronJob through Compass, the Gitea git bridge, and ArgoCD.

A first HyperSync integration is a Camel route you design in Kaoto, select in Compass, and schedule as a CronJob. Compass records that schedule in Git. ArgoCD applies the commit. The route files checked on 4 October 2026 are timer routes with one log step. They are not live connectors.

BPMN diagram: start, design and save the route in Kaoto, select the saved route in Compass, git bridge commits the CronJob, ArgoCD applies the commit, end

Design and save in Kaoto, Compass selects the saved route, the git bridge commits the CronJob, and ArgoCD applies it.

Design and save the route in Kaoto

Open Kaoto at https://kaoto.vitro.lan and design a Camel route. When you save the route, the Kaoto git bridge commits the file to the Gitea repository admin/federal-frontier-platform, branch main, at:

integrations/camel-routes/<filename>.camel.yaml

Select the saved route in Compass

In Compass, open HyperSync and use Refresh routes. The file you saved is listed under Saved route.

On 4 October 2026, Refresh routes listed these files:

  • ceph-capacity.camel.yaml
  • cmdb-ci.camel.yaml
  • keycloak-realms.camel.yaml
  • openstack-projects.camel.yaml
  • vmware-inventory.camel.yaml

These are timer routes with one log step. They are not live connectors to VMware, Ceph, Keycloak, or OpenStack. A filename that names one of those systems does not mean a connector to that system exists.

Create the sync

Pick the route, enter the system of record and a cron schedule, then Create sync.

Compass does not call the Kubernetes API. It asks the git bridge to commit this file:

deploy/overlays/fmc/hypersync/hypersync-<slug>-cronjob.yaml

It also adds that file to kustomization.yaml. The CronJob uses the existing Camel K kit and mounts the saved route.

ArgoCD applies the commit

The ArgoCD app ffo-hypersync applies that commit. The CronJob then shows in the HyperSync fleet.

Verified runs

The CronJob hypersync-cmdb-ci in namespace f3iai ran and logged read configuration items from the CMDB on timer://cmdb. That manifest was committed to the platform repository and synced by ArgoCD.

After the git bridge was fixed to create a missing Gitea file with POST (platform commit 79648717), a publish returned 200 and wrote deploy/overlays/fmc/hypersync/hypersync-vmware-cronjob.yaml for route vmware-inventory.camel.yaml, schedule 0 * * * *. The ArgoCD app ffo-hypersync synced commit 129af1b26b8b8f8fa6da224e1a08c059f47480fb. kubectl showed hypersync-vmware. That route is still a timer route with one log step. It is not a live VMware connector.