Skip to content

Update docs v1 concepts #6351

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
khanhtc1202 merged 2 commits into from
Nov 18, 2025
Merged

Update docs v1 concepts #6351

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8332e90
Update docs v1 concepts page
khanhtc1202 Nov 18, 2025
0b190a3
Refactor docs v1 concepts page
khanhtc1202 Nov 18, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 7 additions & 13 deletions docs/content/en/docs-v1.0.x/concepts/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,12 @@ description: >
Component Architecture
</p>

### Control Plane

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.

### Piped

'`piped`' is a binary, agent component responsible for executing deployments in PipeCD. `Piped` now adopts **plugin-based** **architecture**, transforming from a single-purpose executor into a lightweight runtime capable of runnning any deployment logic defined by plugins. The `piped` component is designed to be stateless.
Expand All @@ -33,12 +39,6 @@ In this architecture, plugins are the actors who execute deployments on behalf o
>**Note:**
>Check out the [PipeCD Community Plugins repository](https://github.com/pipe-cd/community-plugins) to browse available plugins and learn how to create your own.

### Control Plane

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.

### Project

A Project is a logical group of applications managed together by a team of users.
Expand Down Expand Up @@ -78,13 +78,7 @@ When a deployment completes successfully, the running environment matches the co
PipeCD provides 3 different ways to keep your application’s live state consistent with its desired state stored in Git.
Depending on your deployment workflow, you can choose from one of the following sync strategies:

- Quick Sync: A fast, single-step method to sync your deployment with the desired state. PipeCD automatically generates a pipeline composed of predefined Quick Sync stages provided by plugins linked to the application. This is done either through deploy targets specified during application registration on the Control Plane or via the pipeline seclession defined in the application configuration.

```yaml
- name: SYNC
```

Quick Sync is generally used when you need to rapidly apply configuration changes without a gradual rollout.
- Quick Sync: A fast, single-step method to sync your deployment with the desired state. PipeCD automatically generates a pipeline composed of predefined Quick Sync stages provided by plugins linked to the application. Quick Sync is generally used when you need to rapidly apply configuration changes without a gradual rollout.

- Pipeline Sync: A customizable, step-by-step sync process that follows the pipeline you define in your application configuration file. Use Pipeline Sync when you need more control over how updates are rolled out.

Expand Down