Built out the kubernetes_multicluster plugin for PipeCD during my LFX Mentorship, across 30+ merged PRs: canary, primary and baseline rollouts, traffic routing, rollback, plan preview, drift detection and per-cluster deploy status.
merged PRs during the mentorship
30+
deployment stages built
6 of 8
PRs reviewed since, as a maintainer
170+
What changed
Shipped progressive delivery (canary, primary, baseline and traffic routing) across multiple Kubernetes clusters.
Added per-target deploy statuses to the plugin SDK, so operators can see which cluster failed.
Brought the plugin to release standard with docs and a README.
What I worked on
I was the LFX Mentee for the multi-cluster plugin (LFX Mentorship Term 1, 2026).
I designed and implemented the stages, fixes and SDK changes in more than 30 merged PRs.
I wrote the plugin's announcement post on the PipeCD blog.
I built out the kubernetes_multicluster plugin for PipeCD as my LFX Mentorship project. The plugin lets a single PipeCD application deploy to several Kubernetes clusters at once. PipeCD maintainers had started it in 2025 with a basic multi-cluster sync stage; I added the progressive delivery stages the single-cluster plugin supports and took it to release.
Stages
I implemented the core deployment stages one at a time:
Config validation for KubernetesApplicationSpec (#6747)
An initializer hook for Helm repo and OCI registry auth (#6723)
Istio traffic routing: all seven stages green across both clusters.
Per-cluster deploy status
When a stage deploys to several clusters and one fails, operators used to see only "stage failed". I added a DeployTargetStatus type to the plugin SDK and extended ExecuteStageResponse with per-target statuses, in both PipeCD and the standalone Go SDK. The plugin now reports which cluster failed (#6861, piped-plugin-sdk-go #6, #6812).
Release
I also renamed stages to avoid conflicts with the single-cluster plugin, added tests and cleanup PRs, and wrote the plugin documentation page and README to release standard (#6880, #6878, #6977). I wrote about the project in Part 1 and Part 2.
In review
Templating Helm charts from a chart repository or OCI registry, not just local charts (#7465)
Applying per-target kustomize settings in the plan preview (#7437)
Part 2 of the blog post, covering the work after the first six stages (#7464)