How to create a CI/CD pipeline with Auto Deploy to Kubernetes using GitLab and Helm

The author discusses changes and enhancements made to their GitLab CI/CD pipeline for deploying Golang microservices, focusing on improvements such as using GitLab's caching, splitting jobs into multiple steps, and employing Helm charts for application packaging. They abandoned the docker-in-docker approach and opted for using a cache for packages to improve efficiency. The CI/CD process involves setting up directories for Golang's strict project location requirements, caching dependencies in the vendor directory, and building binaries. The testing phase includes running Golang tests with coverage reports, while the deployment stage utilizes GitLab's CI/CD variables with base64 encoded Kubernetes configurations, allowing for flexible management of multiple cluster configurations without native Kubernetes integration. The deployment process can handle multiple application versions by checking and setting the app version in the Chart.yaml file, aiding in either deploying or upgrading releases as required.

No tracked trend matches for this post yet.

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.