Skip to main content
Version: Release Next

Live Deployments in Release

Live Deployments shows the current state of your deployed applications in one place, whether they were deployed by a Release task or by an external tool such as Digital.ai Deploy, Argo CD, or Flux CD.

Release tracks each application through the deployment events that the deployment provider sends, so the dashboard also covers deployments that Release does not orchestrate itself. To bring those deployments into a release flow, use Webhook Event Triggers and the Webhook: Wait for Deployment Event task.

Ways to Set Up Live Deployments​

There are two ways to bring deployments into the Live Deployments dashboard.

  • Onboard new deployments sets up new deployments in Digital.ai Deploy or Argo CD from Release, using the bundled onboarding workflows. Use this when there is nothing deployed yet. For more information, see Onboard New Deployments.
  • Connect to existing deployments exposes applications that already run on a Deploy, Argo CD, or Flux CD server. Use this when you already have working deployments that you want to track in Release. For more information, see Connect to Argo CD Server, Connect to Deploy Server, or Connect to Flux CD Server.

Both approaches need a connection to the deployment server. For more information, see Set Up Connections in Release.

Prerequisites​

Check the requirements for Release and for each deployment provider you plan to track.

Digital.ai Release​

  • Release 24.3 or later, with a Release runner
  • The container plugins for Deploy, Argo CD, and Flux CD, which are included by default
  • Network connectivity between Release and every deployment server
  • Access to the Release web interface

Digital.ai Deploy​

  • Deploy 24.3 or later, running and reachable
  • The Deploy server URL
  • Deploy server credentials with sufficient permissions
  • Target environments configured in Deploy

Argo CD​

  • An Argo CD server running and reachable
  • Administrator access to the Argo CD server
  • The Argo CD server URL
  • Kubernetes cluster access configured for Argo CD
  • Access to configure applications and projects
  • Permission to configure webhook events using the config map that Live Deployments setup generates. For more information, see Argo CD Notification Services - Webhook
  • Permissions configured for the Release integration. For more information, see Configure Permissions for Argo CD Live Deployments

Flux CD​

  • Flux CD running and reachable
  • Administrator access to the Flux CD server
  • The Flux CLI installed and configured
  • Access to the GitOps repository and to the Kubernetes clusters
  • Permission to modify Flux system configurations and to create webhook receivers using the config map that Live Deployments setup generates. For more information, see Flux CD, Setup Webhook Receivers

Set Up Connections in Release​

Before Release can track deployments, connect it to each deployment server you want to track.

Connecting to Digital.ai Deploy​

  1. In Release, navigate to Connections > Digital.ai Deploy Server.
  2. On the New Digital.ai Deploy Server settings page, type the required details to create a connection between the Digital.ai Release and Digital.ai Deploy servers. For more information, see Configure Deploy Server.
  3. Click Test to verify the connection.
  4. Click Save if the test is successful.

Connecting to Argo CD​

  1. Navigate to Connections > ArgoCD: Server.
  2. On the New ArgoCD: Server settings page, type the required details to create a connection between the Digital.ai Release and Argo CD servers. For more information, see Setup Connection to Argo CD Server.
  3. Click Test to verify the connection.
  4. Click Save if the test is successful.

Connecting to Flux CD​

  1. Navigate to Connections > FluxCD API Server (Container).
  2. On the New FluxCD API Server (Container) settings page, type the required details to create a connection between the Digital.ai Release and Flux CD servers. For more information, see Set up Connection to FluxCD Server.
  3. Click Test to verify the connection.
  4. Click Save if the test is successful.