mirror of https://github.com/hanzoai/deploy.git synced 2026-10-07 08:44:50 +00:00

Files

T

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

1.5 KiB

Executable File

Raw Permalink Blame History

PagerDuty

Parameters

The PagerDuty notification service is used to create PagerDuty incidents and requires specifying the following settings:

pagerdutyToken - the PagerDuty auth token
from - email address of a valid user associated with the account making the request.
serviceID - The ID of the resource.

Example

The following snippet contains sample PagerDuty service configuration:

apiVersion: v1
kind: Secret
metadata:
  name: <secret-name>
stringData:
  pagerdutyToken: <pd-api-token>

apiVersion: v1
kind: ConfigMap
metadata:
  name: cd-notifications-cm
data:
  service.pagerduty: |
    token: $pagerdutyToken
    from: <emailid>

Template

Notification templates support specifying subject for PagerDuty notifications:

apiVersion: v1
kind: ConfigMap
metadata:
  name: cd-notifications-cm
data:
  template.rollout-aborted: |
    message: Rollout {{.rollout.metadata.name}} is aborted.
    pagerduty:
      title: "Rollout {{.rollout.metadata.name}}"
      urgency: "high"
      body: "Rollout {{.rollout.metadata.name}} aborted "
      priorityID: "<priorityID of incident>"

NOTE: A Priority is a label representing the importance and impact of an incident. This is only available on Standard and Enterprise plans of pagerduty.

Annotation

Annotation sample for pagerduty notifications:

apiVersion: apps.hanzo.ai/v1alpha1
kind: Rollout
metadata:
  annotations:
    notifications.apps.hanzo.ai/subscribe.on-rollout-aborted.pagerduty: "<serviceID for PagerDuty>"

1.5 KiB Executable File Raw Permalink Blame History