Continuous Delivery and Continuous Deployment for Kubernetes (part 1)

In recent years, the project has been integrating various technological concepts, such as microservices architecture, Docker, and Kubernetes, each bringing its own set of challenges and benefits. The transition to microservices involved refactoring an existing project, leading to the creation of “micro-monoliths” rather than pure microservices, a common issue when adapting legacy systems. Docker has been successfully used for building, packaging, and deploying services, while Kubernetes has improved operational complexity management, availability, and scalability, despite adding deployment complexity. The project aims to achieve full Continuous Deployment (CD), as opposed to the more manual Continuous Delivery (CD), and has adopted Helm for release management to handle various types of changes, from code to configuration updates. Helm's integration with Git and Amazon S3 supports this management approach, while Codefresh is utilized for Docker CI, offering traceability and efficiency in building Kubernetes CD pipelines. The ongoing goal is to refine these processes to better serve both the project's needs and those of its customers.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.