+Control Plane Architecture +
+ A centralized component managing deployment data and provides gRPC API for connecting `piped`s as well as all web-functionalities of PipeCD such as authentication, showing deployment list/details, application list/details, delivery insights... diff --git a/docs/content/en/docs-v0.57.x/concepts/_index.md b/docs/content/en/docs-v0.57.x/concepts/_index.md index f7cb274a29..6c80186569 100644 --- a/docs/content/en/docs-v0.57.x/concepts/_index.md +++ b/docs/content/en/docs-v0.57.x/concepts/_index.md @@ -19,6 +19,11 @@ This component is designed to be stateless, so it can also be run in a single VM ### Control Plane + ++Control Plane Architecture +
+ A centralized component managing deployment data and provides gRPC API for connecting `piped`s as well as all web-functionalities of PipeCD such as authentication, showing deployment list/details, application list/details, delivery insights... diff --git a/docs/content/en/docs-v1.0.x/concepts/_index.md b/docs/content/en/docs-v1.0.x/concepts/_index.md index 4a47604f77..be2529468b 100644 --- a/docs/content/en/docs-v1.0.x/concepts/_index.md +++ b/docs/content/en/docs-v1.0.x/concepts/_index.md @@ -14,6 +14,12 @@ Component Architecture ### Control Plane + ++Control Plane Architecture +
+ The Control Plane is the centralized management service of PipeCD. It coordinates all activities between users, projects, and `piped` instances. The Control Plane remains the backbone of the system but is now fully plugin-aware. Instead of directly handling deployment logic for specific platforms, it interacts with `piped` agents that run plugin binaries, allowing the Control Plane to manage deployments across any platform supported by plugins.