CI/CD & DevOps Architect / Arsitek CI/CD & DevOps
English | Bahasa Indonesia
English
Description
Design and maintain CI/CD pipelines (GitHub Actions, GitLab CI, Buildkite) and manage infrastructure using Docker, Kubernetes (1.30+), and Terraform/OpenTofu.
Orchestration & Integration
Connect with these skills to orchestrate complete workflows:
cloud-hosting-expert — Deployment targets (Vercel, Cloudflare, AWS, Railway)
dependency-upgrade-migrator — Renovate Bot configuration in CI/CD
self-healing-cloud-orchestrator — Auto-remediation and rollback pipelines
logging-error-tracking-expert — Sentry source map upload step in build pipeline
e2e-testing-expert — Automated Playwright & Vitest test steps in CI
zero-trust-secret-vault — CI/CD secret management and injection
production-ready-hardener — Pre-deployment security scanning in CI
Key CI/CD Workflows & Patterns
- Automate Everything: Enforce tests, linting, formatting, and security scans on every PR. Block merges on pipeline failure.
- Dependency Update Bot: Configure Renovate Bot for automated patch/minor updates (
dependency-upgrade-migrator).
- Source Maps Upload: Upload Sentry source maps during build phase (
logging-error-tracking-expert).
- Immutable Artifacts: Build Docker image once, deploy identical image to Staging and Production. Inject environment variables dynamically at runtime.
- Infrastructure as Code: Store all infrastructure configurations (Terraform/OpenTofu, K8s manifests) in version control. No manual web console changes.
- Zero-Trust Secrets: Never commit secrets. Use Infisical, GitHub OIDC, or HashiCorp Vault (
zero-trust-secret-vault).
- Zero-Downtime Deployments: Utilize rolling updates or blue-green deployments.
Implementation Checklist
Trigger Conditions
Trigger when creating GitHub Actions, configuring Dockerfiles, writing Terraform/OpenTofu scripts, setting up Renovate Bot, or configuring deployment pipelines.
Bahasa Indonesia
Deskripsi
Rancang dan pelihara pipeline CI/CD (GitHub Actions, GitLab CI, Buildkite) dan kelola infrastruktur menggunakan Docker, Kubernetes (1.30+), dan Terraform/OpenTofu.
Integrasi Orkestrasi
Hubungkan dengan skill berikut untuk mengorkestrasi alur kerja:
cloud-hosting-expert — Target deployment (Vercel, Cloudflare, AWS, Railway)
dependency-upgrade-migrator — Konfigurasi Renovate Bot di CI/CD
self-healing-cloud-orchestrator — Pipeline auto-remediasi dan rollback
logging-error-tracking-expert — Langkah upload source map Sentry di pipeline build
e2e-testing-expert — Langkah pengujian otomatis Playwright & Vitest di CI
zero-trust-secret-vault — Manajemen dan injeksi rahasia CI/CD
production-ready-hardener — Pemindaian keamanan pra-deployment di CI
Alur Kerja & Pola CI/CD Utama
- Otomatisasi Semuanya: Wajibkan pengujian, linting, pemformatan, dan pemindaian keamanan di setiap PR. Blokir merge jika pipeline gagal.
- Bot Pembaruan Dependensi: Konfigurasi Renovate Bot untuk update otomatis patch/minor (
dependency-upgrade-migrator).
- Upload Source Maps: Upload source maps Sentry pada fase build (
logging-error-tracking-expert).
- Artifak Imutabel: Build image Docker sekali, deploy image yang persis sama ke Staging dan Produksi. Injeksi variabel lingkungan saat runtime.
- Infrastructure as Code (IaC): Simpan semua konfigurasi infrastruktur (Terraform/OpenTofu, manifes K8s) di kontrol versi. Jangan ubah manual via konsol web.
- Manajemen Rahasia (Secrets): Jangan komit rahasia. Gunakan GitHub OIDC, Infisical, atau HashiCorp Vault (
zero-trust-secret-vault).
- Deployment Tanpa Downtime: Manfaatkan pembaruan bergulir (rolling updates) atau blue-green deployments.
Checklist Implementasi
Kondisi Pemicu
Picu saat membuat GitHub Actions, mengkonfigurasi Dockerfile, menulis skrip Terraform/OpenTofu, mengatur Renovate Bot, atau mengatur pipeline deployment.
1---2name: ci-cd-devops-architect3description: Expert guide for continuous integration, deployment pipelines, Docker, Kubernetes, and Infrastructure as Code (IaC) / Panduan ahli untuk CI/CD dan infrastruktur.4---56# CI/CD & DevOps Architect / Arsitek CI/CD & DevOps78[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)910---1112<a name="english"></a>13## English1415### Description16Design and maintain CI/CD pipelines (GitHub Actions, GitLab CI, Buildkite) and manage infrastructure using Docker, Kubernetes (1.30+), and Terraform/OpenTofu.1718## Orchestration & Integration19Connect with these skills to orchestrate complete workflows:20- `cloud-hosting-expert` — Deployment targets (Vercel, Cloudflare, AWS, Railway)21- `dependency-upgrade-migrator` — Renovate Bot configuration in CI/CD22- `self-healing-cloud-orchestrator` — Auto-remediation and rollback pipelines23- `logging-error-tracking-expert` — Sentry source map upload step in build pipeline24- `e2e-testing-expert` — Automated Playwright & Vitest test steps in CI25- `zero-trust-secret-vault` — CI/CD secret management and injection26- `production-ready-hardener` — Pre-deployment security scanning in CI2728### Key CI/CD Workflows & Patterns29- **Automate Everything**: Enforce tests, linting, formatting, and security scans on every PR. Block merges on pipeline failure.30- **Dependency Update Bot**: Configure Renovate Bot for automated patch/minor updates (`dependency-upgrade-migrator`).31- **Source Maps Upload**: Upload Sentry source maps during build phase (`logging-error-tracking-expert`).32- **Immutable Artifacts**: Build Docker image once, deploy identical image to Staging and Production. Inject environment variables dynamically at runtime.33- **Infrastructure as Code**: Store all infrastructure configurations (Terraform/OpenTofu, K8s manifests) in version control. No manual web console changes.34- **Zero-Trust Secrets**: Never commit secrets. Use Infisical, GitHub OIDC, or HashiCorp Vault (`zero-trust-secret-vault`).35- **Zero-Downtime Deployments**: Utilize rolling updates or blue-green deployments.3637### Implementation Checklist38- [ ] Configure branch protection (require passing status checks before merge).39- [ ] Set up multi-stage Docker builds to reduce image size and attack surface.40- [ ] Implement caching for package managers (pnpm, bun, cargo, go mod) in CI.41- [ ] Scan container images for vulnerabilities before registry push.4243### Trigger Conditions44Trigger when creating GitHub Actions, configuring Dockerfiles, writing Terraform/OpenTofu scripts, setting up Renovate Bot, or configuring deployment pipelines.4546---4748<a name="bahasa-indonesia"></a>49## Bahasa Indonesia5051### Deskripsi52Rancang dan pelihara *pipeline* CI/CD (GitHub Actions, GitLab CI, Buildkite) dan kelola infrastruktur menggunakan Docker, Kubernetes (1.30+), dan Terraform/OpenTofu.5354## Integrasi Orkestrasi55Hubungkan dengan skill berikut untuk mengorkestrasi alur kerja:56- `cloud-hosting-expert` — Target deployment (Vercel, Cloudflare, AWS, Railway)57- `dependency-upgrade-migrator` — Konfigurasi Renovate Bot di CI/CD58- `self-healing-cloud-orchestrator` — Pipeline auto-remediasi dan rollback59- `logging-error-tracking-expert` — Langkah upload source map Sentry di pipeline build60- `e2e-testing-expert` — Langkah pengujian otomatis Playwright & Vitest di CI61- `zero-trust-secret-vault` — Manajemen dan injeksi rahasia CI/CD62- `production-ready-hardener` — Pemindaian keamanan pra-deployment di CI6364### Alur Kerja & Pola CI/CD Utama65- **Otomatisasi Semuanya**: Wajibkan pengujian, *linting*, pemformatan, dan pemindaian keamanan di setiap PR. Blokir merge jika *pipeline* gagal.66- **Bot Pembaruan Dependensi**: Konfigurasi Renovate Bot untuk update otomatis patch/minor (`dependency-upgrade-migrator`).67- **Upload Source Maps**: Upload source maps Sentry pada fase build (`logging-error-tracking-expert`).68- **Artifak Imutabel**: Build *image* Docker sekali, *deploy* image yang persis sama ke Staging dan Produksi. Injeksi variabel lingkungan saat runtime.69- **Infrastructure as Code (IaC)**: Simpan semua konfigurasi infrastruktur (Terraform/OpenTofu, manifes K8s) di kontrol versi. Jangan ubah manual via konsol web.70- **Manajemen Rahasia (Secrets)**: Jangan komit rahasia. Gunakan GitHub OIDC, Infisical, atau HashiCorp Vault (`zero-trust-secret-vault`).71- **Deployment Tanpa Downtime**: Manfaatkan pembaruan bergulir (*rolling updates*) atau *blue-green deployments*.7273### Checklist Implementasi74- [ ] Konfigurasi perlindungan cabang (wajib lulus status check sebelum merge).75- [ ] Siapkan multi-stage Docker builds untuk mengurangi ukuran image dan permukaan serangan.76- [ ] Implementasikan caching untuk package managers (pnpm, bun, cargo, go mod) di workflow CI.77- [ ] Pindai image kontainer untuk kerentanan sebelum push ke registry.7879### Kondisi Pemicu80Picu saat membuat GitHub Actions, mengkonfigurasi Dockerfile, menulis skrip Terraform/OpenTofu, mengatur Renovate Bot, atau mengatur *pipeline deployment*.