Architecture overview

This page describes the architecture of control plane.

Component Architecture

The control plane is a centralized part of PipeCD. It contains several services as below to manage the application, deployment data and handle all requests from pipeds and web clients:

Server

server handles all incoming gRPC requests from pipeds, web clients, incoming HTTP requests such as auth callback from third party services. It also serves all web assets including HTML, JS, CSS… This service can be easily scaled by updating the pod number.

Cache

cache is a single pod service for caching internal data used by server service. Currently, this cache service is powered by redis. You can configure the control plane to use a fully-managed redis cache service instead of launching a cache pod in your cluster.

Ops

ops is a single pod service for operating PipeCD owner’s tasks. For example, it provides an internal web page for adding and managing projects; it periodically removes the old data; it collects and saves the deployment insights.

Data Store

Data store is a storage for storing model data such as applications and deployments. This can be a fully-managed service such as GCP Firestore, GCP Cloud SQL or AWS RDS (currently we choose MySQL v8 as supported relational data store). You can also configure the control plane to use a self-managed MySQL server. When installing the control plane, you have to choose one of the provided data store services.

File Store

File store is a storage for storing stage logs, application live states. This can be a fully-managed service such as GCP GCS, AWS S3, or a self-managed service such as Minio. When installing the control plane, you have to choose one of the provided file store services.


Last modified March 18, 2022: Release v0.27.0 (#3417) (8c3c92da)