deploy/docs/operator-manual/notifications/troubleshooting.md at dependabot/go_modules/sigs.k8s.io/controller-runtime-0.25.2

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.8 KiB

Raw Permalink Blame History

cd admin notifications is a CLI command group that helps to configure the controller settings and troubleshoot issues. Full command details are available in the command reference.

Global flags

The following global flags are available for all sub-commands:

--config-map - path to the file containing cd-notifications-cm ConfigMap. If not specified then the command loads cd-notification-cm ConfigMap using the local Kubernetes config file.
--secret - path to the file containing cd-notifications-secret ConfigMap. If not specified then the command loads cd-notification-secret Secret using the local Kubernetes config file. Additionally, you can specify :empty to use empty secret with no notification service settings.

Examples:

Get a list of triggers configured in the local config map:

cd admin notifications trigger get \
  --config-map ./cd-notifications-cm.yaml --secret :empty

Trigger notification using in-cluster config map and secret:

cd admin notifications template notify \
  app-sync-succeeded guestbook --recipient slack:cd admin notifications

Kustomize

If you are managing cd-notifications config using Kustomize you can pipe whole kustomize build output into stdin using --config-map - flag:

kustomize build ./cd-notifications | \
  cd-notifications \
  template notify app-sync-succeeded guestbook --recipient grafana:cd \
  --config-map -

How to get it

On your laptop

You can download the cd CLI from the GitHub release attachments.

The binary is available in the quay.io/argoproj/cd image. Use the docker run and volume mount to execute binary on any platform.

Example:

docker run --rm -it -w /src -v $(pwd):/src \
  quay.io/argoproj/cd:<version> \
  /app/cd admin notifications trigger get \
  --config-map ./cd-notifications-cm.yaml --secret :empty

In your cluster

SSH into the running cd-notifications-controller pod and use kubectl exec command to validate in-cluster configuration.

Example

kubectl exec -it cd-notifications-controller-<pod-hash> \
  /usr/local/bin/cd admin notifications trigger get

Commands

The following commands may help debug issues with notifications:

Errors

{!docs/operator-manual/notifications/troubleshooting-errors.md!}

2.8 KiB Raw Permalink Blame History