CI/CD Overview

General Workflow

1. Source Code Management: Store your application code in a version control system (e.g., GitHub, GitLab, Bitbucket).
2. CI Pipeline Trigger: A code change triggers your CI pipeline.
3. Build and Test: The CI tool builds your application, runs tests (unit, integration, etc.), and packages it into a container image (e.g., Docker).
4. Push to Registry: The container image is pushed to a container registry (e.g., Docker Hub).
5. CD Pipeline Trigger: A successful CI pipeline triggers your CD pipeline.
6. Connect to HKE Cluster: Your CD tool retrieves your cluster’s kubeconfig file for secure access. This file is typically stored as a secret in your CI/CD tool.
7. Deploy to Cluster: The CD tool uses kubectl or Helm to deploy your application to your HKE cluster. This might involve updating existing resources or creating new ones.
8. Verify Deployment: Run post-deployment tests to ensure your application is working as expected in the cluster environment.