Ci/Cd on marktaguiad.dev

Breaking Away from Traditional CI/CD: Introducing GitOps with ArgoCD

marktaguiad@marktaguiad.dev (Mark Taguiad) — Fri, 17 Apr 2026 00:00:00 +0000

Info

Read on related blog first; Building CI/CD Pipeline - A Not-So-Comprehensive Guide.

Traditional CI/CD pipelines tightly couple build, test, and deployment into a single workflow. Once a change passes tests, the pipeline pushes directly to the target environment. While simple, this model limits visibility, auditability, and control over deployments.

This approach shifts deployment responsibility away from the CI pipeline into a dedicated GitOps repository, where the desired state of the system lives. Deployment is no longer “pushed” — it is pulled and reconciled by ArgoCD.

Istio: A/B Testing and Canary Deployment

marktaguiad@marktaguiad.dev (Mark Taguiad) — Fri, 03 Apr 2026 00:00:00 +0000

A/B testing and Canary Deployment allows you to route traffic between different versions of your application to compare performance, behavior, or user experience.

With Istio, you can control traffic without changing application code—just by configuring the service mesh.

Replicate this using this repo.

1kubectl apply -k kube/ab-testing/demo

A/B Testing vs Canary Deployment

Aspect	Canary Deployment	A/B Testing
Purpose	Safe rollout	Experimentation
Traffic split	Gradual (10% → 100%)	Fixed (often 50/50)
Decision basis	Errors, latency	User behavior, metrics
End goal	Replace old version	Pick best variant
Versions	Usually same feature	Different UX/features

A/B Testing

Labels

Label your deployments properly.

Building CI/CD Pipeline - A Not-So-Comprehensive Guide

marktaguiad@marktaguiad.dev (Mark Taguiad) — Wed, 01 Apr 2026 00:00:00 +0000

Info

This is just a personal notes, so some information here might need clarification and researching.

A CI/CD pipeline is an automated workflow that moves code from commit to production. It standardizes build, test, and deployment stages to improve release speed, reliability, and consistency.

CI/CD integrates development and operations through automation, reducing manual errors and enabling frequent, incremental delivery.

CI/CD Overview

Continuous Integration (CI)

Frequent code merges into a shared repository
Automated builds and test execution
Early detection of integration issues

Continuous Delivery

Ensures code is always in a deployable state
Deployment requires manual approval

Continuous Deployment

Fully automated release to production
Triggered after successful test validation

Pipeline Architecture

A typical CI/CD pipeline consists of sequential automated stages: