[{"data":1,"prerenderedAt":40},["ShallowReactive",2],{"blog-tag-en-gitops":3},[4,15,23,32],{"path":5,"title":6,"description":7,"date":8,"tags":9},"\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,13,14],"k3s","kubernetes","ci-cd","gitops","security",{"path":16,"title":17,"description":18,"date":19,"tags":20},"\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,21,13,22],"edge-computing","fleet-management",{"path":24,"title":25,"description":26,"date":27,"tags":28},"\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,29,30,13,31],"platform-engineering","internal-developer-platform","managed-kubernetes",{"path":33,"title":34,"description":35,"date":36,"tags":37},"\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,38,13,39],"canary-release","argo-rollouts",1786354669179]