[{"data":1,"prerenderedAt":81},["ShallowReactive",2],{"blog-tag-en-gitops":3},[4,16,24,31,39,48,56,64,72],{"path":5,"title":6,"description":7,"date":8,"tags":9},"\u002Fblog\u002Fen\u002Fcicd-pipeline-devsecops-gate-design-four-layers","Still Bolting Security Checks Onto Your CI\u002FCD Pipeline Without Deciding Where They Belong? A Four-Layer Model for DevSecOps Gate Design","You've adopted SAST, DAST, and container scanning — yet incidents still slip into production. This article reframes CI\u002FCD pipeline security as a four-layer design problem and walks through concrete implementation patterns for K3s\u002FKubernetes environments.","2026-08-28",[10,11,12,13,14,15],"k3s","kubernetes","ci-cd","devsecops","admission-control","gitops",{"path":17,"title":18,"description":19,"date":20,"tags":21},"\u002Fblog\u002Fen\u002Fkubernetes-gitops-branch-antipattern-fleet-scaling","Your dev\u002Fstaging\u002Fprod Branches Are a Time Bomb: Why Kubernetes GitOps Really Breaks","Splitting dev\u002Fstaging\u002Fproduction by Git branch is a GitOps anti-pattern that undermines Kubernetes' declarative foundations. Learn why drift happens, how to migrate to a directory-based, trunk-based setup, and how to design for fleet-scale growth.","2026-08-10",[10,11,15,22,23],"argocd","devops",{"path":25,"title":26,"description":27,"date":28,"tags":29},"\u002Fblog\u002Fen\u002Fkubernetes-image-signing-sigstore-supply-chain","Anyone Can Rewrite an Image Tag. Why Kubernetes Needs Sigstore-Backed Signing to Prove Provenance","Container image signing explained: tags can be overwritten by anyone, and passing CI tests doesn't guarantee the image running in production is the one you built. Learn how Sigstore and Kyverno work together to reject unsigned images on Kubernetes\u002FK3s, integrated into a GitOps workflow.","2026-08-06",[10,11,12,15,30],"security",{"path":32,"title":33,"description":34,"date":35,"tags":36},"\u002Fblog\u002Fen\u002Fk3s-edge-fleet-declarative-management","One Device's Troubleshooting Is a Funny Story. A Thousand Devices Is a Business Risk: How Rancher Fleet Rescues K3s Edge Operations from Tribal Knowledge","Fleet management for K3s edge operations breaks down once you're troubleshooting devices one at a time by hand. Here's how declarative management and Rancher Fleet let you design edge operations that don't depend on any single person.","2026-08-03",[10,11,37,15,38],"edge-computing","fleet-management",{"path":40,"title":41,"description":42,"date":43,"tags":44},"\u002Fblog\u002Fen\u002Fplatform-engineering-kubernetes-idp-managed-k3s","Stop Handing Developers Raw Kubernetes: The 'Hiding' Philosophy of Platform Engineering, and Kubo's Answer","An explainer on the relationship between platform engineering and Kubernetes — the design philosophy of shielding developers from K8s complexity, the three pillars of building an IDP, and managed K3s as an alternative.","2026-07-16",[11,10,45,46,15,47],"platform-engineering","internal-developer-platform","managed-kubernetes",{"path":49,"title":50,"description":51,"date":52,"tags":53},"\u002Fblog\u002Fen\u002Fcanary-release-kubernetes-auto-rollback-gitops","Why Every Team Ends Up at the Same CI\u002FCD Wall — Designing 'Safe-to-Break' Kubernetes Deployments with Canary Releases and Automated Rollback","Most production incidents happen because teams deploy everything at once. This article walks through how to design canary releases, automated rollback, and monitoring on Kubernetes using Argo Rollouts and GitOps — with practical steps small teams can actually sustain.","2026-07-15",[11,10,12,54,15,55],"canary-release","argo-rollouts",{"path":57,"title":58,"description":59,"date":60,"tags":61},"\u002Fblog\u002Fen\u002Fargocd-gitops-kubernetes-guide","Getting Started with ArgoCD GitOps: Practical Kubernetes Declarative Deployment","A practical guide to GitOps-based Kubernetes declarative deployment with ArgoCD. Covers repository structure, Sync Waves, ApplicationSets, and multi-cluster management.","2026-05-27",[22,15,11,12,62,63],"deployment-automation","declarative-management",{"path":65,"title":66,"description":67,"date":60,"tags":68},"\u002Fblog\u002Fen\u002Ffluxcd-vs-argocd-comparison","FluxCD vs ArgoCD: A Comprehensive GitOps Tool Comparison","An in-depth comparison of FluxCD and ArgoCD covering architecture, UI, multi-cluster support, resource usage, security models, Helm integration, and use-case recommendations.",[69,22,15,11,70,71],"fluxcd","comparison","cncf",{"path":73,"title":74,"description":75,"date":60,"tags":76},"\u002Fblog\u002Fen\u002Fhelm-charts-best-practices","Helm Chart Development Best Practices 2025","A comprehensive guide to Helm chart development best practices in 2025. Covers template design, testing strategies, OCI registries, security, and ci-cd integration.",[77,11,78,79,80,15],"helm","package-management","chart-development","best-practices",1792488948366]