Skip to main content

Architecture

Conductor requires two Kubernetes resources to be installed on your cluster to power the Conductor dashboard, Diagrid CLI and Kubernetes operator. The Conductor Agent Deployment and Logs Collector DaemonSet will be automatically installed into their own namespace and will communicate outbound only to Diagrid Cloud.

For the step-by-step communication flow, see below. For a list of pre-requisites, read Cluster pre-requisites.

Conductor Architecture

  1. User visits Diagrid Conductor via internet browser or uses the Diagrid CLI.

  2. User is authenticated via username/password or through Single-Sign-On identity provider.

  3. Conductor dashboard is populated with data from Diagrid Cloud. Desired Kubernetes cluster configuration is sent to Diagrid Cloud.

  4. Diagrid agent deployed on users' Kubernetes cluster reconciles desired Dapr configuration and sends specified data outbound such as metrics, cluster configuration and health data. Connection is encrypted using TLS.

  5. Diagrid agent manages the Dapr control plane on users' Kubernetes cluster and collects metrics.

  6. Dapr control plane injects Dapr sidecars into users' configured Kubernetes application pods.

  7. Diagrid logs collector collects Dapr sidecar logs.