CI/CD

Overview In the previous post, we installed the core components of the CI/CD system: Harbor registry, Argo Events, and Argo Workflows. In this post, we will integrate these three components with the previously installed ArgoCD to complete a full CI/CD pipeline and build a GitOps-based project automation system. Integrating CI/CD with GitOps The integration of traditional CI systems with GitOps is a natural evolution. Traditional CI focused on detecting code changes, building, and testing, while GitOps focuses on declaratively managing deployment state and automatically synchronizing it. Combining these two approaches enables building a fully automated pipeline from code changes to automatic deployment. ...

Overview In the previous post, we installed Vault in the homelab Kubernetes cluster and set up a secrets management system. In this post, we will explore how to install and configure three core components that form the foundation of a CI/CD system: Harbor registry, Argo Events, and Argo Workflows. Components of the CI/CD System To build a complete CI/CD pipeline in a homelab environment, the following core components are required: ...

What is GitOps? GitOps, a concept first introduced by Weaveworks in 2017, focuses on continuous deployment (CD) in cloud-native environments, particularly in Kubernetes-based systems. It involves managing all infrastructure configurations and application settings as code and versioning them through a Git repository. Push-Based Deployment Strategy The push-based approach operates similarly to traditional CI/CD pipelines, with the following key features and processes: Build and Deployment Process Build Phase A CI pipeline is triggered by a developer’s code push The CI server builds and tests the code Container images are built and uploaded to a registry Deployment Phase ...