Project Lightning Talk: PipeCDv1 Is Here! Leverage The Power Of Plugin Architecture - Khanh Tran

This talk covers the PipeCD project, which is a GitOps style progressive delivery platform for Kubernetes and other platforms. The speaker, Kang, who is a software engineer and maintainer of PipeCD, explains the architecture of PipeCD, consisting of a control plane and an agent called piped. The latest update introduces PipeCD V1 in an alpha state, adopting a plugin architecture that separates platform-specific code from the main codebase, promoting modularity and ease of use. Kang also discusses enhancements to the app configuration, making it more accessible for users and simplifying transitions for those upgrading from version 0. Additionally, he highlights ongoing development for multi-cluster plugins and the release of a PipeCD plugin SDK to foster community contributions and plugins. The session concludes with information on connecting with the PipeCD community for further collaboration.

Hello everyone. I'm Kang, I'm a software engineer at CyberZ and I'm maintainer of the PipeCD project. My talk is about the PipeCD project and some update from it. So, for people who knew to PipeCD, basically PipeCD does what FluxCD and Argo CD do for Kubernetes for Kubernetes and for the other platform as well. It's an GitOps style progressive delivery platform that provide consistent deployment and operation experience

for any application platform. Before V1 supported platform was Kubernetes, Terraform, ECS, Lambda, and GCP Cloud Run. So, from an overview, PipeCD consists of two component, the control plane and the agent we call it piped. The control plane is the centric component manage deployment data, provides the RPC API to connect with piped agent as well as the UI. While the piped is a single binary, you can run

it anywhere you want like in the port or serverless task handler or anywhere. This architect have separated platform and the dev team scope. And if you are a platform engineer and want a solution for centric CD for the whole company with a different platform like I said, Kubernetes, ECS, Lambda, anything at the same time, then you can consider PipeCD. For more about PipeCD internal, please check out

the official website of So, let's check out the update from project. We just released the PipeCD V1 at alpha state and it adopt the plugin architecture. In detail, instead of including all platform supporting code into the PipeCD agent code base, and ship it as a single binary, all the platform and state execution specific code is now separate from the PipeCD D They are built separately and distributed

as a plug-in of the Pipe D agent. The Pipe D and its plug-in communicate via CRPC protocol and user wind control with plug-in should be instant and config what to do use via the Pipe D configuration. With the update of the Pipe D plug-in architecture, we also rebuild the Pipe CD app config abstraction. Uh you can see here on the left is the old Pipe D configuration

file uh for Pipe for uh Kubernetes application. It requires specific application guy that type correct with the platform like for Kubernetes application, it need to be guy Kubernetes app. And um also we have an input spec that need to contain the field that fit all the Pipe CD supported guy that lead to hard to follow documentation and implementation uh from outside. And uh you can see on

the right is the new Pipe D app uh with guy set to generic application and platform config will be moved under the plug-in specific with will be easier for both doc and implementation. Of course, there are some other change in the abstraction as well, but this is just uh what you can feel about the new abstraction of Pipe CD. And if you are using the Pipe CD

V0 up to now, uh we also uh prepare a Pipe CD or command that help you reformat the app configuration. So, you don't need to worry about the abstraction update. You can check out the QR code I uh left here uh that link to the migration documentation. So, um uh most of uh state is killed uh in Pipe D0 already released as a plug-in in V1 including

Kubernetes Terraform with with approval, Screwdriver, and Analyst. Except some would be the plug-in and have uh PipeCD to execute the state that you define in your pipeline. Under deployment um is for now we deploying uh we developing the ECS and Kubernetes multi-cluster plug-in. The Kubernetes multi-cluster plug-in is the new one. Uh it's aimed to support deploying your application manifests to multiple clusters at once and will be

released independently from the Kubernetes plug-in. Uh it's an a very uh seeing ability equipped by the plug-in architecture of PipeCD. We also working on V1 documentation and building the guide from making PipeCD plug-in that uh will be released shortly. Uh the PipeCD plug-in SDK in Go has released in uh at version 0.3.0 and based on that SDK, some community build plug-in are already available, which include uh

Open ToFu and SQL Dev Uh some other notable we plug-in are Azure Function and Ansible. All the community plug-in are hosted under the PipeCD community plug-in repo. If you have any idea of you free or if you interest on in making one for yourself, please just check out the community plug-in repo or note for detail. Uh and uh finally, I put here some connection point for joining

the PipeCD community. We have bi-weekly meeting and you can check the schedule and uh how to join via the QR. We also have the booth pavilion tomorrow morning. So, if you feel interest and want to discuss, just stop by and chat. Thank you all and have a great KubeCon. All right, thank you, buddy.