CI: Self-Hosting GitHub Actions Runners on K8s
Self-hosting GitHub Actions runners on an on-premise Kubernetes cluster via ARC, configured through ArgoCD — how the listener picks up jobs and spins up ephemeral pods
Self-hosting GitHub Actions runners on an on-premise Kubernetes cluster via ARC, configured through ArgoCD — how the listener picks up jobs and spins up ephemeral pods
Integrating Harbor as a self-hosted container registry for a K8s cluster — why over a cloud CR, dev architecture, and a fault-tolerant production design
ACR interaction in the automated CI/CD pipeline
Comparing Blue Green and Canary deployment strategies on Kubernetes with Argo Rollouts — flow, traffic shaping, and when each fits
Domain modeling notes from the KIA DCE project — a hierarchical division tree, a parent-children content model, and a draft/publish state machine
Why we centralized logs with Grafana + Loki and metrics with Prometheus, plus the single-cluster and multi-cluster (hub-and-spoke) integration patterns
Atomic multi-collection writes via mongoose ClientSession, wrapped in a reusable withTransaction helper
A GitHub Actions job that updates Helm values in a GitOps repo, then hands off to ArgoCD
A GitHub Actions workflow that builds and pushes container images to a self-hosted Harbor registry on ARC runners
컴퓨터처럼 생각하기 (기본 → 심화) 정리글