Argo Events

Listens for events (webhooks, schedules, streams) and triggers workflows in response

Argo Events wires sensors to event sources: webhooks, artifact updates, schedules. Automation reacts to actual events instead of cron jobs polling for change.

ArgoCD configuration

Excerpt from argocd-apps/values.yaml in the argocd-apps chart, with annotations added for this site: 

argo-events:
  application: true
  project: cluster-services
  # false
  autoSync: false

Chart values

The full argo-events/values.yaml from the service's own chart: 

argo-events:
  # -- Provide a name in place of `argo-events`
  nameOverride: argo-events

  createAggregateRoles: true

  crds:
    install: true
    keep: true

  ## Argo Events controller
  controller:
    name: controller-manager

    rbac:
      enabled: true
      namespaced: false

    replicas: 1

    serviceAccount:
      create: true
      name: "controller-manager-sa"
      automountServiceAccountToken: true

    ## Events controller metrics configuration
    metrics:
      enabled: false

  ## Argo Events admission webhook
  webhook:
    enabled: false
    name: events-webhook
    revisionHistoryLimit: 5
    replicas: 1
    port: 443

    serviceAccount:
      create: true
      name: "webhook-sa"
      automountServiceAccountToken: true

Trade-offs

Decision. Event sensors for automation

Alternative. Cron jobs that poll for change

Why. Sensors fire on the event itself, so latency and duplicate handling are handled by the platform instead of each script.

← Back to GitOps & Delivery · All service groups