Configure Automated Canary Deployments in Spinnaker

Learn how to configure Kayenta using the Armory Operator.

Kayenta Overview

Kayenta is the Spinnaker service that performs automated canary analysis. The goal of Kayenta is to provide you with confidence that a deployment is safe through automation and intelligence.

Enable Kayenta

Add the following to your SpinnakerService manifest:

        enabled: true   # Enable/disable canary analysis

Configure Kayenta

The following example is a SpinnakerService manifest. The example config uses Datadog as the metrics provider and stores canary configs and analysis in a GCS bucket:

kind: SpinnakerService
  name: spinnaker
        enabled: true   # Enable/disable canary analysis
          - name: datadog
            - name: test-account
                baseUrl: <some-URL> # The base URL to the Datadog server.
              apiKey: <encrypted-secret> # Your org’s unique Datadog API key. See Supports encrypted value.
              applicationKey: <encrypted-secret> #Your Datadog application key. See Supports encrypted value.
              - METRICS_STORE
              - OBJECT_STORE
          - name: google
            enabled: true   # Enable/disable Google provider
            - name: my-google-account
              project: my-project-id       # The Google Cloud Platform project the Canary service uses to consume GCS and Stackdriver.
              jsonPath: gcp-sa.json        # File name of a JSON service account that Spinnaker uses for credentials. This is only needed if Spinnaker is not deployed on a Google Compute Engine VM or needs permissions not afforded to the VM it is running on. See for more information. This field supports using "encryptedFile" secret references.
              bucket: my-bucket            # The name of a storage bucket that your specified account has access to. If you specify a globally unique bucket name that doesn't exist, Kayenta creates that bucket.
              bucketLocation: us-central-1 # Required if the bucket you specify doesn't exist. In that case, the bucket gets created in that location. See
              rootFolder: kayenta          # The root folder in the chosen bucket to place all of the Canary service's persistent data in (Default: kayenta).
              supportedTypes:              # Array of: METRICS_STORE, CONFIGURATION_STORE, OBJECT_STORE
              - OBJECT_STORE
            gcsEnabled: true               # Whether or not GCS is enabled as a persistent store (Default: false).
            stackdriverEnabled: false      # Whether or not Stackdriver is enabled Stackdriver as a metrics service (Default: false).
            metadataCachingIntervalMS: 60000 # Number of milliseconds to wait between caching the names of available metric types for use in building canary configs. (Default: 60000)
        reduxLoggerEnabled: true           # Whether or not to enable redux logging in the canary module in deck (Default: true).
        defaultJudge: NetflixACAJudge-v1.0 # Name of canary judge to use by default (Default: NetflixACAJudge-v1.0).
        stagesEnabled: true                # Whether or not to enable canary stages in deck (Default: true).
        templatesEnabled: true             # Whether or not to enable custom filter templates for canary configs in deck (Default: true).
        showAllConfigsEnabled: true        # Whether or not to show all canary configs in deck, or just those scoped to the current application (Default: true).
        ...  # rest of config omitted for brevity
      gcp-sa.json: |

For an overview of how to configure metrics providers see Canary Config. For Dynatrace and AWS Cloudwatch providers, see Use Canary Analysis with Dynatrace or AWS CloudWatch Integration Plugin.

What’s next

For information about how to use canary deployments, see Use Automatic Canary Analysis in Spinnaker.

Last modified December 19, 2023: (13976a9f)