Skip to main content

​
Hybrid Ingestion Runner deployment

The Hybrid Runner acts as a proxy between the Collate Server and your Argo Workflows installation (the orchestration system). Communication is established via a secure WebSocket connection (TLS), initiated outbound from your cluster. Collate never stores or accesses the secrets used to connect to your data sources — those are managed by your own infrastructure and retrieved at runtime by the Runner.

​
Architecture Overview

Hybrid Runner architecture diagram showing the WebSocket connection between Collate SaaS and the Hybrid Runner, and the flow from Argo Workflows through ingestion pods to Kubernetes Secrets

​
Requirements

​
Hardware

A GKE cluster with at least 2 worker nodes. Each node requires:
  • 2 x86 vCPUs
  • 8 GiB Memory
  • 64 GiB Storage

​
Software

  • Kubernetes 1.28 or later
  • Helm CLI and kubectl installed locally
  • Argo Workflows 3.7 (installed automatically by the Helm chart)