tags / GitOps
8 posts
Hardcoding deployment strategy into pipelines creates a hidden coupling that makes platforms less reliable. The Strategy pattern explains how to make canary, blue/green, and progressive delivery first-class platform concerns.
Pipelines that run kubectl apply directly are automated but invisible. The Command pattern explains why GitOps is architecturally sound — not just a convention — and what you gain from separating the definition of a change from its execution.
Manual reconciliation doesn't scale. The Kubernetes controller loop is the Observer pattern at cluster scale. Learn how operators, Argo Rollouts, and External Secrets Operator implement this pattern — and how to decide when to write your own.
Terraform, Helm, GitOps... ¿para entrenar modelos? Sí.
Welcome to Day 15 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’re diving into workflow automation for Kubernetes using Kustomize and Skaffold, two tools that simplify managing and deploying Kubernetes configurations
Welcome to Day 14 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’ll focus on securing Kubernetes clusters, covering runtime security and policy enforcement to ensure your applications and infrastructure are protected from vulnerabilities and misconfigurations.
Welcome to Day 13 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’re focusing on monitoring and observability, key components for maintaining the health, performance, and reliability of your applications in Kubernetes.
Welcome to Day 12 of the Zero to Platform Engineer in 30 Days challenge! 🚀 Today, we’re diving deeper into GitOps by exploring Argo Rollouts, a powerful tool for managing progressive delivery strategies like canary and blue-green deployments.