In my previous blog post, CodeZero 301, I shared with you Part 3 of a four-part series directed at introducing you to the CodeZero platform and some of its useful tools and features for Kubernetes developers. Part 3 introduced you to the concepts behind Halyard, CodeZero’s next generation build and deployment feature that enables developers to ship code easier, faster, and with a higher level of quality. In that article I discussed Continuous Integration, Continuous Delivery, and Continuous Deployment, the processes you should understand to get the most out of Halyard. In this fourth and final article in this series, I walk you through how Halyard works, and how it can help.
Halyard is an opinionated build and deployment feature for developers using Kubernetes, that streamlines the software delivery pipeline and makes it simple to implement, so that developers are freed from time-consuming DevOps configurations; they can simply focus on writing and shipping their code, fearlessly. With just a little bit of knowledge of Kubernetes, a Docker image, and some configuration (done through a UI), a developer can set up a powerful and robust pipeline without getting bogged down in traditional CI/CD.
You can read all about Halyard in this Medium article.