GitHub Actions CI/CD Pipeline

This directory contains the GitHub Actions workflow for the Calculator App CI/CD pipeline.

Pipeline Stages

The CI/CD pipeline consists of the following stages:

1. Unit Testing - Runs the test suite using Vitest
2. Static Code Analysis - Performs linting with ESLint
3. Build - Creates a production build of the application
4. Docker Image Creation - Builds a Docker image using a multi-stage Dockerfile
5. Docker Image Scan - Scans the image for vulnerabilities using Trivy
6. Docker Image Push - Pushes the image to GitHub Container Registry
7. Update Kubernetes Deployment - Updates the Kubernetes deployment file with the new image tag

How the Kubernetes Deployment Update Works

The "Update Kubernetes Deployment" stage:

1. Runs only on pushes to the main branch
2. Uses a shell script to update the image reference in the Kubernetes deployment file
3. Commits and pushes the updated deployment file back to the repository
4. This ensures that the Kubernetes manifest always references the latest image

Required Secrets

The workflow requires the following GitHub secrets:

• GITHUB_TOKEN - Automatically provided by GitHub Actions, used for pushing to the repository and the container registry

Continuous Deployment

For full continuous deployment, you would need to:

1. Set up a Kubernetes operator like Flux or ArgoCD to watch for changes in the repository
2. Configure it to automatically apply changes to the Kubernetes manifests
3. This would complete the CI/CD pipeline by automatically deploying the new image to your Kubernetes cluster

Manual Deployment

If you're not using a GitOps approach with an operator, you can manually apply the updated deployment:

kubectl apply -f kubernetes/deployment.yaml

Or set up a webhook to trigger the deployment when the manifest is updated.