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

2.4 KiB

Executable File

Raw Permalink Blame History

Grafana

To be able to create Grafana annotation with cd-notifications you have to create an API Key inside your Grafana.

Available parameters :

apiURL - the server url, e.g. https://grafana.example.com
apiKey - the API key for the serviceaccount
insecureSkipVerify - optional bool, true or false
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.

Login to your Grafana instance as admin
On the left menu, go to Configuration / API Keys
Click "Add API Key"
Fill the Key with name Hanzo CD Notification, role Editor and Time to Live 10y (for example)
Click on Add button
Store apiKey in cd-notifications-secret Secret and Copy your API Key and define it in cd-notifications-cm ConfigMap

apiVersion: v1
kind: ConfigMap
metadata:
  name: cd-notifications-cm
data:
  service.grafana: |
    apiUrl: https://grafana.example.com/api
    apiKey: $grafana-api-key

apiVersion: v1
kind: Secret
metadata:
  name: <secret-name>
stringData:
  grafana-api-key: api-key

Create a template in argo-notifications-cm Configmap This will be used to pass the (required) text of the annotation to Grafana (or re-use an existing one) As there is no specific template for Grafana, you must use the generic message:

apiVersion: v1
kind: ConfigMap
metadata:
  name: cd-notifications-cm
data:
  templates:
    template.app-deployed: |
      message: Application {{.app.metadata.name}} is now running new version of deployments manifests.

Create subscription for your Grafana integration

apiVersion: apps.hanzo.ai/v1alpha1
kind: Application
metadata:
  annotations:
    notifications.apps.hanzo.ai/subscribe.<trigger-name>.grafana: tag1|tag2 # list of tags separated with |

Change the annotations settings

2.4 KiB Executable File Raw Permalink Blame History

Grafana

2.4 KiB

Executable File

Raw Permalink Blame History