Do We Need Yet Another CD Tool?

### Overview In this talk, Ram from the Cloud Foundry Foundation explores the rapid expansion of continuous delivery (CD) tools within the cloud-native ecosystem. Addressing the recurring emergence of new open-source, vendor-driven, and proprietary solutions, the session questions whether the community truly requires yet another CD tool or whether emerging requirements could instead be integrated as features into existing platforms.

### Key Topics - **Proliferation and Tool Sprawl:** The ecosystem has seen a massive surge in CD tools (such as Dagger, PipeCD, Tekton, Argo, Spinnaker, and Screwdriver), making it challenging to keep track of new entrants. - **Adoption Reality vs. Familiarity:** The speaker outlines a personal progression from learning about numerous tools, to testing them, using them in production, and ultimately realizing that Jenkins remains the primary tool he can comfortably configure for production use despite identifying with modern cloud-native tools. - **Origins of New Projects:** Many CD tools emerge when engineering teams encounter niche requirements that existing options cannot handle, leading to internal walled-garden projects that eventually become open-source or CD Foundation projects. - **Feature vs. Standalone Tool:** A central dilemma is whether niche use cases justify spinning up entirely new projects rather than contributing capabilities directly into established platforms like Argo.

### Technical Details - **Tekton vs. Argo Comparison:** - **Workflows and Primitives:** Tekton focuses on configuring pipelines composed of composite tasks forming larger workflows, whereas Argo offers distinct components for workflows, CD, and rollouts. - **User Experience:** Argo includes a graphical user interface (UI), which makes adoption easier compared to relying strictly on heavy YAML engineering. - **Kubernetes Integration:** Tekton is highly declarative and deeply tied into the Kubernetes ecosystem via custom resources, ideal when everything—including CI/CD—runs on Kubernetes. Argo allows teams to step outside of Kubernetes for parts of CI/CD. - **Extensibility:** Both tools provide extensibility through plugins, integrations, or custom resource definitions. - **Generalizability to Other Tools:** The speaker observed that the trade-offs and distinctions between Tekton and Argo closely mirror comparisons between other tools, such as Spinnaker versus Screwdriver.

### Takeaways While diversity and niche innovation in the CI/CD ecosystem are valuable, continuous tool sprawl creates redundancy and steep learning curves. The speaker urges the technology community to critically evaluate whether new standalone CD tools are genuinely necessary before starting new projects.