search

cncf / sandbox

Applications for Sandbox go here! ⏳📦🧪
Apache License 2.0
132 stars 22 forks source link

[Sandbox] PipeCD #12

Closed khanhtc1202 closed 1 year ago

khanhtc1202 commented 1 year ago

Application contact emails

khanhtc1202@gmail.com, nghialv2607@gmail.com, kenta.kozuka@gmail.com, nao.7ken@gmail.com, stormcat24@stormcat.io

Project Summary

One CD for All {applications, platforms, operations}

Project Description

PipeCD is a GitOps-style continuous delivery platform that provides consistent deployment and operations experience for any application.

The idea of PipeCD is to make a unified interface to deploy different kinds of applications (currently PipeCD supports Kubernetes, Terraform, GCP Cloud Run, AWS Lambda, and AWS ECS). The reason behind that idea is we are faced with systems that mix multiple platforms running applications, and also at the company scale, not every team has the same idea/experience/taste when choosing the team stack (CD included), and all gaps and diversity between teams’ decisions should be respected and treated carefully.

With the introduction of PipeCD, we will have a standard and easy option to archive requirements for a CD at the company level.

Characteristics of the project

Visibility

Automation

Safety and Security

Multi-provider & Multi-Tenancy

Org repo URL

https://github.com/pipe-cd

Project repo URL

https://github.com/pipe-cd/pipecd

Additional repos

https://github.com/pipe-cd/examples https://github.com/pipe-cd/actions-plan-preview https://github.com/pipe-cd/actions-event-register https://github.com/pipe-cd/orb-pipecd

Website URL

https://pipecd.dev

Live demo or playground

https://play.pipecd.dev/applications?project=play

Roadmap

For the next few releases (until next year's first quarter):

For further releases (next year):

Roadmap context

No response

Contributing Guide

https://pipecd.dev/docs/contribution-guidelines/

Code of Conduct (CoC)

https://github.com/pipe-cd/pipecd/blob/master/CODE_OF_CONDUCT.md

Adopters

No response

Contributing or Sponsoring Org

No response

Maintainers file

https://github.com/pipe-cd/pipecd/blob/master/MAINTAINERS.md

IP Policy

Trademark and accounts

Why CNCF?

Currently, PipeCD is at production-ready stage with several nice features that we thought many developers would love to have for a CD based on our experience while developing it. By joining CNCF, we are seeking visibility and community adoption so that we can have a better point of view on what we built. With the aim we list in the roadmap, we wish for community ideas and contributions to make it comes true. We also wish for guidance from CNCF while building the PipeCD community as well.

Benefit to the Landscape

First of all, the PipeCD's idea is to support a wide range (aim to open support all) of cloud-native platforms. It’s not just about deployment for Kubernetes applications which already had many contributions and support from the community but other kinds of applications as well. By introducing a unified interface to deploy different kinds of applications, the cost to migrate between platforms, human error while deploying, etc would be reduced. The PipeCD's idea respects the diversity of the existing systems as well.

Besides, adding a new option as a CD tool will help accelerate the evolution of the CD area, the community would notice more about supporting different kinds of applications.

Cloud Native 'Fit'

PipeCD is built for cloud-native applications, it supports cloud-native applications in mind.

Cloud Native 'Integration'

PipeCD works well as the CD for Kubernetes, Knative app (GCP CloudRun), Terraform, and so on. Internally, PipeCD uses Helm (and also Kustomize) to manage deployments for applications that run on Kubernetes platform.

Cloud Native Overlap

No response

Similar projects

ArgoCD, FluxCD

Product or Service to Project separation

N/A

Project presentations

https://speakerdeck.com/nghialv/a-consistent-delivery-process-with-gitops-style-for-any-application-on-any-platform

Project champions

No response

Additional information

No response

khanhtc1202 commented 1 year ago

The application for PipeCD is ready for review, PTAL when you guys have time 🙏

amye commented 1 year ago

We'll be reviewing these in January 2023 at the earliest!

dims commented 1 year ago

@khanhtc1202 could you please add some notes on how you compare/contrast your submission with flux and argo?

khanhtc1202 commented 1 year ago

Hi @dims, sorry for the late! About the comparison between my submission (pipecd) with other CNCF projects (flux and argo in this case), it's different in the vision at first:

The vision of pipecd is to be a tool that allows developers to deploy and manage any application to any platform. It is a bit as same as another project called Waypoint (https://www.waypointproject.io/), but we focus only on CD (which means there will be no build processes supported)

Besides, we have a FAQ for comparison in some specified fields; it can be accessed from here https://pipecd.dev/docs/faq/#4-what-are-the-differences-between-pipecd-and-fluxcd https://pipecd.dev/docs/faq/#5-what-are-the-differences-between-pipecd-and-argocd

AloisReitbauer commented 1 year ago

Feel free to also submit a lighting talk for the TAG App Delivery workshop at KubeCon: https://docs.google.com/forms/d/e/1FAIpQLSc2ruf4q2k7nWCZyEp0Wy_nW9z5bsf0ES0ARqZrhwnKEkk5Ig/viewform

khanhtc1202 commented 1 year ago

Thanks @AloisReitbauer; We have sent an application, plz check it out when you have time 😄

justincormack commented 1 year ago

It is unclear to me who currently owns the code, there is no "Contributing or Sponsoring Org" but there is a CLA https://github.com/pipe-cd/pipecd/blob/master/CLA.md but that only refers to "The Project". Does CyberAgent Inc own any rights to the code?

khanhtc1202 commented 1 year ago

@justincormack Currently the code's right belongs to PipeCD authors - the PipeCD team working at CyberAgent, Inc. as mentioned. But the company (CyberAgent, Inc.) and the team are willing and happy to contribute all to the community. Please guide us to fix CLA if needed.

justincormack commented 1 year ago

@khanhtc1202 I don't think a CLA that assigns to a group of authors (not a legal entity) is a good idea - IANAL but I doubt it is workable. I would remove the CLA completely.

khanhtc1202 commented 1 year ago

I would remove the CLA completely.

Thanks for the comment. So the point is removing CLA, right? I will share with the team and update later.

amye commented 1 year ago

/vote-sandbox

git-vote[bot] commented 1 year ago

Vote created

@amye has called for a vote on [Sandbox] PipeCD (#12).

The members of the following teams have binding votes:

Team
@cncf/cncf-toc

Non-binding votes are also appreciated as a sign of support!

How to vote

You can cast your vote by reacting to this comment. The following reactions are supported:

In favor Against Abstain
👍 👎 👀

Please note that voting for multiple options is not allowed and those votes won't be counted.

The vote will be open for 7days. It will pass if at least 66% of the users with binding votes vote In favor 👍. Once it's closed, results will be published here as a new comment.

khanhtc1202 commented 1 year ago

Hi TOC members, thank you so much for your hard-working! I re-watched the Sandbox review meeting record today (May 9th) and want to respond to the unclear difference between PipeCD and Argo/Flux comments in the meeting. ref: https://github.com/cncf/sandbox/issues/12#issuecomment-1378194527

To us, the PipeCD idea is based on one interface for various applications kinds that respect diversity. Currently, we don’t have any simple solution to archive GitOps for CloudRun, Terraform (and many other application kinds that are not K8s), and we think that’s a miss. From K8s users’ point of view, PipeCD does not have much difference compared to other K8s major CDs (Argo/Flux), but we think cloud native is not just about K8s but other platforms as well. That’s the big difference from the other users’ point of view.

By introducing one interface which brings K8s easy-to-get GitOps for other platforms, we can also open the opportunity for other platform users to save their cost on moving to K8s when they have resources for that since the CD between “them” are the same already. The PipeCD project has no conflict with the current major K8s CDs’ approaches but also tries to clear the gap by supporting many other cloud-native platforms that are not K8s besides supporting the K8s itself.

If that’s not what you said about the unclear difference in the meeting, please help me understand it. :pray:

amye commented 1 year ago

/check-vote

git-vote[bot] commented 1 year ago

Vote status

So far 16.67% of the users with binding vote are in favor (passing threshold: 66%).

Summary

In favor Against Abstain Not voted
2 0 0 10

Binding votes (2)

User Vote Timestamp
rochaporto In favor 2023-05-09 18:52:40.0 +00:00:00
cathyhongzhang In favor 2023-05-09 16:08:30.0 +00:00:00

Non-binding votes (4)

 | User | Vote | Timestamp | | ---- | :---: | :-------: | | khanhtc1202 | In favor | 2023-05-09 16:39:54.0 +00:00:00 | | nghialv | In favor | 2023-05-10 1:08:19.0 +00:00:00 | | EBBach | In favor | 2023-05-10 5:07:50.0 +00:00:00 | | minhquang4334 | In favor | 2023-05-10 6:20:04.0 +00:00:00 |
khanhtc1202 commented 1 year ago

About the community-related comments, I want to make clear what we mentioned:

Please let me know if you have any further questions.

tegioz commented 1 year ago

/check-vote

git-vote[bot] commented 1 year ago

Vote status

So far 18.18% of the users with binding vote are in favor (passing threshold: 66%).

Summary

In favor Against Abstain Not voted
2 0 0 9

Binding votes (2)

User Vote Timestamp
cathyhongzhang In favor 2023-05-09 16:08:30.0 +00:00:00
rochaporto In favor 2023-05-09 18:52:40.0 +00:00:00

Non-binding votes (4)

 | User | Vote | Timestamp | | ---- | :---: | :-------: | | khanhtc1202 | In favor | 2023-05-09 16:39:54.0 +00:00:00 | | nghialv | In favor | 2023-05-10 1:08:19.0 +00:00:00 | | EBBach | In favor | 2023-05-10 5:07:50.0 +00:00:00 | | minhquang4334 | In favor | 2023-05-10 6:20:04.0 +00:00:00 |
khanhtc1202 commented 1 year ago

@justincormack We just removed the CLA as your advice, thank you! https://github.com/pipe-cd/pipecd/pull/4335

amye commented 1 year ago

/check-vote

git-vote[bot] commented 1 year ago

Vote status

So far 45.45% of the users with binding vote are in favor (passing threshold: 66%).

Summary

In favor Against Abstain Not voted
5 0 0 6

Binding votes (5)

User Vote Timestamp
cathyhongzhang In favor 2023-05-09 16:08:30.0 +00:00:00
rochaporto In favor 2023-05-09 18:52:40.0 +00:00:00
TheFoxAtWork In favor 2023-05-15 14:20:56.0 +00:00:00
nikhita In favor 2023-05-15 14:41:34.0 +00:00:00
kgamanji In favor 2023-05-15 15:54:06.0 +00:00:00

Non-binding votes (5)

 | User | Vote | Timestamp | | ---- | :---: | :-------: | | khanhtc1202 | In favor | 2023-05-09 16:39:54.0 +00:00:00 | | nghialv | In favor | 2023-05-10 1:08:19.0 +00:00:00 | | EBBach | In favor | 2023-05-10 5:07:50.0 +00:00:00 | | minhquang4334 | In favor | 2023-05-10 6:20:04.0 +00:00:00 | | kentakozuka | In favor | 2023-05-11 23:05:01.0 +00:00:00 |
erinaboyd commented 1 year ago

👍

khanhtc1202 commented 1 year ago

/check-vote

git-vote[bot] commented 1 year ago

Vote status

So far 63.64% of the users with binding vote are in favor (passing threshold: 66%).

Summary

In favor Against Abstain Not voted
7 0 0 4

Binding votes (7)

User Vote Timestamp
nikhita In favor 2023-05-15 14:41:34.0 +00:00:00
TheFoxAtWork In favor 2023-05-15 14:20:56.0 +00:00:00
mauilion In favor 2023-05-16 14:58:52.0 +00:00:00
dzolotusky In favor 2023-05-16 22:02:52.0 +00:00:00
kgamanji In favor 2023-05-15 15:54:06.0 +00:00:00
rochaporto In favor 2023-05-09 18:52:40.0 +00:00:00
cathyhongzhang In favor 2023-05-09 16:08:30.0 +00:00:00

Non-binding votes (5)

 | User | Vote | Timestamp | | ---- | :---: | :-------: | | khanhtc1202 | In favor | 2023-05-09 16:39:54.0 +00:00:00 | | nghialv | In favor | 2023-05-10 1:08:19.0 +00:00:00 | | EBBach | In favor | 2023-05-10 5:07:50.0 +00:00:00 | | minhquang4334 | In favor | 2023-05-10 6:20:04.0 +00:00:00 | | kentakozuka | In favor | 2023-05-11 23:05:01.0 +00:00:00 |
sivchari commented 1 year ago

/check-vote

git-vote[bot] commented 1 year ago

Votes can only be checked once a day.

git-vote[bot] commented 1 year ago

Vote closed

The vote passed! 🎉

72.73% of the users with binding vote were in favor (passing threshold: 66%).

Summary

In favor Against Abstain Not voted
8 0 0 3

Binding votes (8)

User Vote Timestamp
@rochaporto In favor 2023-05-09 18:52:40.0 +00:00:00
@kgamanji In favor 2023-05-15 15:54:06.0 +00:00:00
@dzolotusky In favor 2023-05-16 22:02:52.0 +00:00:00
@TheFoxAtWork In favor 2023-05-15 14:20:56.0 +00:00:00
@RichiH In favor 2023-05-17 8:48:18.0 +00:00:00
@mauilion In favor 2023-05-16 14:58:52.0 +00:00:00
@cathyhongzhang In favor 2023-05-09 16:08:30.0 +00:00:00
@nikhita In favor 2023-05-15 14:41:34.0 +00:00:00

Non-binding votes (10)

 | User | Vote | Timestamp | | ---- | :---: | :-------: | | @khanhtc1202 | In favor | 2023-05-09 16:39:54.0 +00:00:00 | | @EBBach | In favor | 2023-05-10 5:07:50.0 +00:00:00 | | @minhquang4334 | In favor | 2023-05-10 6:20:04.0 +00:00:00 | | @kentakozuka | In favor | 2023-05-11 23:05:01.0 +00:00:00 | | @HoangNguyen689 | In favor | 2023-05-17 2:59:25.0 +00:00:00 | | @sivchari | In favor | 2023-05-17 3:32:28.0 +00:00:00 | | @kurochan | In favor | 2023-05-17 3:36:16.0 +00:00:00 | | @ThanhChinhBK | In favor | 2023-05-17 3:43:00.0 +00:00:00 | | @ono-max | In favor | 2023-05-17 6:42:02.0 +00:00:00 | | @nghialv | In favor | 2023-05-17 15:04:44.0 +00:00:00 |