This document will give details about how you create production ready CI/CD infrastructure with Kubernetes with recommended CI/CD tools integrations .

What is CI/CD :

Continuous Integration :

Continuous integration is about automating build and test processes to make sure the resulting software is in a good state, ideally every time a developer changes code. CI helps development teams avoid “integration hell” where the software works on individual developers’ machines, but it fails when all developers combine (or “integrate”) their code.

Continuous Delivery :

Continuous Delivery goes one step further to automate a software release, which typically involves packaging the software for deployment in a production-like environment. The goal of Continuous Delivery is to make sure the software is always ready to go to production, even if the team decides not to do it for business reasons.

Continuous Deployment :

Continuous Deployment is a process that automatically deploys the results of Continuous Delivery into the final production environment, usually every time a developer changes code (assuming all automated tests pass).

By adopting both Continuous Integration and Continuous Deployment, you not only reduce risks and catch bugs quickly, but also move rapidly to working software.

With low-risk releases, you can quickly adapt to business requirements and user needs. This allows for greater collaboration between ops and delivery, fueling real change in your organization, and turning your release process into a business advantage.

Use following tech-stack to create CI/CD Pipeline.

All this are open source tools and available with 0 cost , if there is strong use case for your CI/CD framework where you want to go with enterprise versions to have 24 hour support you can install enterprise versions . For enterprise edition you need to pay for each year for community support and upgrades .

#kubernetes #devops

Building, Testing and Deploying with Kubernetes (CI/CD)
3.65 GEEK