Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getcollate.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Defining workflow fields

It is possible to override workflow fields using custom definitions. A typical use case would be to define tolerations or pod affinity/antiaffinity. 
config:
  ingestionPods:
    customConfig:
      enabled: true
      workflowParams:
        tolerations:
          - key: team
            effect: NoSchedule
            opeartor: Equal
            value: data-science
In the same fashion, container fields can be updated using the key config.ingestionPods.customConfig.containerParams: 
config:
  ingestionPods:
    customConfig:
      enabled: true
      containerParams:
        env:
          - name: HTTP_PROXY
            value: http://corp-proxy.svc:8080
          - name: HTTPS_PROXY
            value: http://corp-proxy.svc:8080
          - name: NO_PROXY
            value: ".svc, .mycorp.internal"
Defining custom fields was added in Hybrid runner helm chart version 1.12.5.

​
Running multiple instances in the same cluster

As the embedded Argo Workflows is a cluster-wide application, deploying multiple production instances of the Hybrid Runner in a single cluster only requires one of them to provision the Argo Workflows service. For the subsequent instances the relevant configuration would be: 

      argoWorkflows:
        enabled: false
      config:
        argoWorkflows:
          endpoint: http://argo-workflows-server.argo-workflows.svc:2746