Skip to content

Latest commit

 

History

History
143 lines (117 loc) · 5.84 KB

resource_hooks.md

File metadata and controls

143 lines (117 loc) · 5.84 KB
Raw

Resource Hooks

Overview

Synchronization can be configured using resource hooks. Hooks are ways to run scripts before, during, and after a Sync operation. Hooks can also be run if a Sync operation fails at any point. Some use cases for hooks are:

  • Using a PreSync hook to perform a database schema migration before deploying a new version of the app.
  • Using a Sync hook to orchestrate a complex deployment requiring more sophistication than the Kubernetes rolling update strategy.
  • Using a PostSync hook to run integration and health checks after a deployment.
  • Using a SyncFail hook to run clean-up or finalizer logic if a Sync operation fails.
  • Using a PostDelete hook to run clean-up or finalizer logic after all Application resources are deleted. Please note that PostDelete hooks are only deleted if the delete policy matches the aggregated deletion hooks status and not garbage collected after the application is deleted.

Usage

Hooks are simply Kubernetes manifests tracked in the source repository of your Argo CD Application annotated with argocd.argoproj.io/hook, e.g.:

apiVersion: batch/v1
kind: Job
metadata:
  generateName: schema-migrate-
  annotations:
    argocd.argoproj.io/hook: PreSync

During a Sync operation, Argo CD will apply the resource during the appropriate phase of the deployment. Hooks can be any type of Kubernetes resource kind, but tend to be Pod, Job or Argo Workflows. Multiple hooks can be specified as a comma separated list.

The following hooks are defined:

Hook Description
PreSync Executes prior to the application of the manifests.
Sync Executes after all PreSync hooks completed and were successful, at the same time as the application of the manifests.
Skip Indicates to Argo CD to skip the application of the manifest.
PostSync Executes after all Sync hooks completed and were successful, a successful application, and all resources in a Healthy state.
SyncFail Executes when the sync operation fails.
PostDelete Executes after all Application resources are deleted. Available starting in v2.10.

Generate Name

Named hooks (i.e. ones with /metadata/name) will only be created once. If you want a hook to be re-created each time either use BeforeHookCreation policy (see below) or /metadata/generateName.

Selective Sync

Hooks are not run during selective sync.

Hook Deletion Policies

Hooks can be deleted in an automatic fashion using the annotation: argocd.argoproj.io/hook-delete-policy.

apiVersion: batch/v1
kind: Job
metadata:
  generateName: integration-test-
  annotations:
    argocd.argoproj.io/hook: PostSync
    argocd.argoproj.io/hook-delete-policy: HookSucceeded

Multiple hook delete policies can be specified as a comma separated list.

The following policies define when the hook will be deleted.

Policy Description
HookSucceeded The hook resource is deleted after the hook succeeded (e.g. Job/Workflow completed successfully).
HookFailed The hook resource is deleted after the hook failed.
BeforeHookCreation Any existing hook resource is deleted before the new one is created (since v1.3). It is meant to be used with /metadata/name.

Note that if no deletion policy is specified, Argo CD will automatically assume BeforeHookCreation rules.

Sync Status with Jobs/Workflows with Time to Live (ttl)

Jobs support the ttlSecondsAfterFinished field in the spec, which let their respective controllers delete the Job after it completes. Argo Workflows support a ttlStrategy property that also allow a Workflow to be cleaned up depending on the ttl strategy chosen.

Using either of the properties above can lead to Applications being OutOfSync. This is because Argo CD will detect a difference between the Job or Workflow defined in the git repository and what's on the cluster since the ttl properties cause deletion of the resource after completion.

However, using deletion hooks instead of the ttl approaches mentioned above will prevent Applications from having a status of OutOfSync even though the Job or Workflow was deleted after completion.

Using A Hook To Send A Slack Message

The following example uses the Slack API to send a Slack message when sync completes or fails:

apiVersion: batch/v1
kind: Job
metadata:
  generateName: app-slack-notification-
  annotations:
    argocd.argoproj.io/hook: PostSync
    argocd.argoproj.io/hook-delete-policy: HookSucceeded
spec:
  template:
    spec:
      containers:
      - name: slack-notification
        image: curlimages/curl
        command:
          - "curl"
          - "-X"
          - "POST"
          - "--data-urlencode"
          - "payload={\"channel\": \"#somechannel\", \"username\": \"hello\", \"text\": \"App Sync succeeded\", \"icon_emoji\": \":ghost:\"}"
          - "https://hooks.slack.com/services/..."
      restartPolicy: Never
  backoffLimit: 2
apiVersion: batch/v1
kind: Job
metadata:
  generateName: app-slack-notification-fail-
  annotations:
    argocd.argoproj.io/hook: SyncFail
    argocd.argoproj.io/hook-delete-policy: HookSucceeded
spec:
  template:
    spec:
      containers:
      - name: slack-notification
        image: curlimages/curl
        command: 
          - "curl"
          - "-X"
          - "POST"
          - "--data-urlencode"
          - "payload={\"channel\": \"#somechannel\", \"username\": \"hello\", \"text\": \"App Sync failed\", \"icon_emoji\": \":ghost:\"}"
          - "https://hooks.slack.com/services/..."
      restartPolicy: Never
  backoffLimit: 2