Files
zeekayandHanzo Dev 446e343a3d cd: annotations are cd.hanzo.ai, API group is apps.hanzo.ai
Two corrections on top of the naming pass, both found by checking the live
cluster rather than the source.

The rename had silently changed the user-facing annotation key from
argocd.argoproj.io/sync-wave to cd.argoproj.io/sync-wave — 63 live
Applications carry the old key, so deploying that would have ignored every
sync-wave and broken fleet deploy ordering. The key is now cd.hanzo.ai/*,
and universe 575650286 moves the ApplicationSet template that stamps it, so
the controller regenerates all 63 consistently.

The API group in code said argoproj.io/v1alpha1 in 157 places while the
cluster has served apps.hanzo.ai/v1alpha1 since 2026-07-23 (the CRDs are
applications.apps.hanzo.ai). Code now matches what is actually served.

The legacy applications.argoproj.io/app-name label had ZERO live users, so it
went with the rest. foo.argoproj.io test fixtures became foo.example.com —
arbitrary test domains should not carry a vendor name.

go build ./... exit 0.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-28 16:32:14 -07:00

6.3 KiB
Executable File

Webhook

The webhook notification service allows sending a generic HTTP request using the templatized request body and URL. Using Webhook you might trigger a Jenkins job, update GitHub commit status.

Parameters

The Webhook notification service configuration includes following settings:

  • url - the url to send the webhook to
  • headers - optional, the headers to pass along with the webhook
  • basicAuth - optional, the basic authentication to pass along with the webhook
  • insecureSkipVerify - optional bool, true or false
  • retryWaitMin - Optional, the minimum wait time between retries. Default value: 1s.
  • retryWaitMax - Optional, the maximum wait time between retries. Default value: 5s.
  • retryMax - Optional, the maximum number of retries. Default value: 3.
  • maxIdleConns - optional, maximum number of idle (keep-alive) connections across all hosts.
  • maxIdleConnsPerHost - optional, maximum number of idle (keep-alive) connections per host.
  • maxConnsPerHost - optional, maximum total connections per host.
  • idleConnTimeout - optional, maximum amount of time an idle (keep-alive) connection will remain open before closing, e.g. '90s'.

Retry Behavior

The webhook service will automatically retry the request if it fails due to network errors or if the server returns a 5xx status code. The number of retries and the wait time between retries can be configured using the retryMax, retryWaitMin, and retryWaitMax parameters.

The wait time between retries is between retryWaitMin and retryWaitMax. If all retries fail, the Send method will return an error.

Configuration

Use the following steps to configure webhook:

1 Register webhook in cd-notifications-cm ConfigMap:

apiVersion: v1
kind: ConfigMap
metadata:
  name: cd-notifications-cm
data:
  service.webhook.<webhook-name>: |
    url: https://<hostname>/<optional-path>
    headers: #optional headers
    - name: <header-name>
      value: <header-value>
    basicAuth: #optional username password
      username: <username>
      password: <api-key>
    insecureSkipVerify: true #optional bool

2 Define template that customizes webhook request method, path and body:

apiVersion: v1
kind: ConfigMap
metadata:
  name: cd-notifications-cm
data:
  template.github-commit-status: |
    webhook:
      <webhook-name>:
        method: POST # one of: GET, POST, PUT, PATCH. Default value: GET 
        path: <optional-path-template>
        body: |
          <optional-body-template>
  trigger.<trigger-name>: |
    - when: app.status.operationState.phase in ['Succeeded']
      send: [github-commit-status]

3 Create subscription for webhook integration:

apiVersion: apps.hanzo.ai/v1alpha1
kind: Application
metadata:
  annotations:
    notifications.apps.hanzo.ai/subscribe.<trigger-name>.<webhook-name>: ""
  1. TLS configuration (optional)

If your webhook server uses a custom TLS certificate, you can configure the notification service to trust it by adding the certificate to the cd-tls-certs-cm ConfigMap as shown below:

apiVersion: v1
kind: ConfigMap
metadata:
  name: cd-tls-certs-cm
data:
  <hostname>: |
    -----BEGIN CERTIFICATE-----
    <TLS DATA>
    -----END CERTIFICATE-----

NOTE: If the custom certificate is not trusted, you may encounter errors such as:

Put \"https://...\": x509: certificate signed by unknown authority

Adding the server's certificate to cd-tls-certs-cm resolves this issue.

Examples

Set GitHub commit status

apiVersion: v1
kind: ConfigMap
metadata:
  name: cd-notifications-cm
data:
  service.webhook.github: |
    url: https://api.github.com
    headers: #optional headers
    - name: Authorization
      value: token $github-token

2 Define template that customizes webhook request method, path and body:

apiVersion: v1
kind: ConfigMap
metadata:
  name: cd-notifications-cm
data:
  service.webhook.github: |
    url: https://api.github.com
    headers: #optional headers
    - name: Authorization
      value: token $github-token

  template.github-commit-status: |
    webhook:
      github:
        method: POST
        path: /repos/{{call .repo.FullNameByRepoURL .app.spec.source.repoURL}}/statuses/{{.app.status.operationState.operation.sync.revision}}
        body: |
          {
            {{if eq .app.status.operationState.phase "Running"}} "state": "pending"{{end}}
            {{if eq .app.status.operationState.phase "Succeeded"}} "state": "success"{{end}}
            {{if eq .app.status.operationState.phase "Error"}} "state": "error"{{end}}
            {{if eq .app.status.operationState.phase "Failed"}} "state": "error"{{end}},
            "description": "Hanzo CD",
            "target_url": "{{.context.cdUrl}}/applications/{{.app.metadata.name}}",
            "context": "continuous-delivery/{{.app.metadata.name}}"
          }

Start Jenkins Job

apiVersion: v1
kind: ConfigMap
metadata:
  name: cd-notifications-cm
data:
  service.webhook.jenkins: |
    url: http://<jenkins-host>/job/<job-name>/build?token=<job-secret>
    basicAuth:
      username: <username>
      password: <api-key>

type: Opaque

Send form-data

apiVersion: v1
kind: ConfigMap
metadata:
  name: cd-notifications-cm
data:
  service.webhook.form: |
    url: https://form.example.com
    headers:
    - name: Content-Type
      value: application/x-www-form-urlencoded

  template.form-data: |
    webhook:
      form:
        method: POST
        body: key1=value1&key2=value2

Send Slack

apiVersion: v1
kind: ConfigMap
metadata:
  name: cd-notifications-cm
data:
  service.webhook.slack_webhook: |
    url: https://hooks.slack.com/services/xxxxx
    headers:
    - name: Content-Type
      value: application/json

  template.send-slack: |
    webhook:
      slack_webhook:
        method: POST
        body: |
          {
            "attachments": [{
              "title": "{{.app.metadata.name}}",
              "title_link": "{{.context.cdUrl}}/applications/{{.app.metadata.name}}",
              "color": "#18be52",
              "fields": [{
                "title": "Sync Status",
                "value": "{{.app.status.sync.status}}",
                "short": true
              }, {
                "title": "Repository",
                "value": "{{.app.spec.source.repoURL}}",
                "short": true
              }]
            }]
          }