The New Stack today is releasing its latest ebook, “CI/CD With Kubernetes,” the third and final in our Kubernetes ecosystem series. It lays the foundation for understanding and building your team’s practices and pipelines for delivering — and continuously improving — applications on Kubernetes.
Kubernetes is the cloud management software of choice. But like other large-scope, cloud software projects, it’s so complex that its value is only fully determined when it’s put into practice within an organization. With its capabilities growing at such a pace, Kubernetes’ ability to scale forces questions about how an organization manages its own teams and adopts DevOps practices.
Kubernetes is increasingly being used as a platform for application deployment, defined by the combined forces of DevOps, continuous delivery and observability. When employed together, these three forces deliver applications faster, more efficiently and closer to what customers want and demand.
The New Stack’s new 118-page ebook is written by independent technology consultants who are experts in application design and delivery with containers on Kubernetes. These topics are discussed in four chapters that include:
- DevOps Patterns by Rob Scott of ReactiveOps.
- Cloud-Native Application Patterns by Janakiram MSV, principal analyst at Janakiram & Associates.
- Continuous Delivery with Spinnaker by Craig Martin, senior vice president of engineering at Kenzan.
- Monitoring in the Cloud-Native Era by a team of engineers from Container Solutions.
DevOps Is Key to Delivering Applications on Kubernetes
Application delivery on Kubernetes starts by building applications as a set of microservices in a container-based, cloud-native architecture. But DevOps practices are what truly transform the application architectures of an organization; they are the basis for all of the patterns and practices that make applications run on Kubernetes. And DevOps transformation only comes with aligning an organization’s values with the ways it develops application architectures.
In this newly optimized means to an organization’s cloud-native transformation, Kubernetes is the enabler — it’s not a complete solution. Your organization must implement the tools and practices best suited to your own business needs and structure in order to realize the full promise of this open source platform. The Kubernetes project documentation itself says so.
Kubernetes “does not deploy source code and does not build your application. Continuous Integration, Delivery, and Deployment (CI/CD) workflows are determined by organization cultures and preferences as well as technical requirements.”
How is that done? It’s not a set of rules. It’s a set of practices that flow into the organization and affect how application architectures are developed. This is DevOps, and its currents are now deep inside organizations with modern application architectures, manifested through continuous delivery.