# GitOps Published articles for GitOps. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Beyond the sync: Argo CD needs an Enterprise Control Plane DevFeed: [Beyond the sync: Argo CD needs an Enterprise Control Plane]() Original publisher: [Read original article]() Author: Eric Minick Sudarshan Purohit Published: 2026-09-16T20:28:57.610955Z Content type: opinion Language: en Sources: [Harness Blog]() Topics: [argo-cd](), [GitOps](), [Orchestration](), [DevOps](), [Platform Engineering](), [Deployment](), [Artificial Intelligence]() Tags: [argo-cd](), [deployment](), [gitops](), [governance](), [orchestration](), [platform-engineering](), [verification]() ### AI overview This article argues that Argo CD's manifest synchronization is only one part of enterprise software delivery. It describes how scaling GitOps can create operational toil and Argo sprawl, and proposes an enterprise control plane with workflow orchestration, governance, and deployment verification. ### Source excerpt Scaling GitOps? Argo CD is great for syncing manifests, but enterprise delivery requires workflow orchestration, governance, and AI verification. | Blog ## Implementing GitOps from Infrastructure to DB Operators to Unify Ops for Kubernetes Databases DevFeed: [Implementing GitOps from Infrastructure to DB Operators to Unify Ops for Kubernetes Databases]() Original publisher: [Read original article]() Author: Sucahyo Ardy Prasetiyo Published: 2026-09-16T08:57:10Z Content type: tutorial Language: en Sources: [SeveralNines]() Topics: [GitOps](), [Kubernetes](), [Terraform](), [argo-cd](), [ClusterControl](), [Databases](), [opentofu]() Tags: [argo-cd](), [clustercontrol](), [databases](), [gitops](), [hybrid-operations](), [infrastructure](), [kubernetes](), [opentofu](), [sovereign-dbaas](), [terraform]() ### AI overview This article describes a layered GitOps approach for Kubernetes database platforms: manage infrastructure with Terraform or OpenTofu, manage Kubernetes deployments with Argo CD, and standardize operations for operator-managed databases with ClusterControl. It explains how declarative configuration and drift reconciliation differ between Terraform and Argo CD, and compares infrastructure automation options including Atlantis and Flux tf-controller. ### Source excerpt Most platform teams already use GitOps for their Kubernetes apps. The config lives in Git, Argo CD applies it, and deployments are predictable. But look one layer down and things get messy. Infrastructure setup is often still done by hand, running Terraform locally or through scattered scripts. Database operations, especially for databases running through Kubernetes [...] The post Implementing GitOps from Infrastructure to DB Operators to Unify Ops for Kubernetes Databases appeared first on Severalnines. ## Using the Komodo MCP Server to Manage Docker Infrastructure with AI Assistants DevFeed: [Using the Komodo MCP Server to Manage Docker Infrastructure with AI Assistants]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-15T12:38:26Z Content type: tutorial Language: en Sources: [Virtualization Howto]() Topics: [Homelab](), [Model Context Protocol (MCP)](), [Docker](), [Docker Compose](), [GitOps](), [Artificial Intelligence]() Tags: [ai](), [automation](), [containers](), [docker](), [gitops](), [home-lab](), [home-server](), [infrastructure](), [mcp]() ### AI overview This tutorial introduces the Komodo MCP Server, which connects AI assistants such as Claude and GitHub Copilot to Komodo for managing Docker environments. It describes natural-language control of containers, stacks, deployments, servers, builds, repositories, and related infrastructure through the Model Context Protocol. ### Source excerpt There are so many cool projects now that we have access to in the the realm of home lab, especially when it comes to automation and AI Ops for our... The post I Gave AI Control of My Docker Home Lab With Komodo MCP appeared first on Virtualization Howto. ## Using Komodo to Manage and Update Docker Compose Stacks Across Multiple Hosts DevFeed: [Using Komodo to Manage and Update Docker Compose Stacks Across Multiple Hosts]() Original publisher: [Read original article]() Author: Brandon Lee Published: 2026-09-12T12:32:29Z Content type: tutorial Language: en Sources: [Virtualization Howto]() Topics: [Docker](), [Docker Compose](), [Homelab](), [Open Source](), [GitOps]() Tags: [containers](), [docker](), [docker-compose](), [gitops](), [home-lab](), [home-server](), [open-source]() ### AI overview The article explains how Komodo, an open source platform, can centrally manage Docker servers, containers, Compose stacks, and deployments across multiple hosts, reducing the need to update each stack manually. ### Source excerpt There are SO many tools out there that allow you to keep your containers updated and I have used just about all of them, including Watchtower, Dockcheck, and others. Running... The post I Stopped Manually Updating My Docker Container Stacks. I Use This Instead appeared first on Virtualization Howto. ## From Bottleneck to Breakthrough: Centralizing GitOps at Enterprise Scale with VCF 9.1.1 DevFeed: [From Bottleneck to Breakthrough: Centralizing GitOps at Enterprise Scale with VCF 9.1.1]() Original publisher: [Read original article]() Author: vmwareblogs Published: 2026-09-03T14:03:46Z Content type: article Language: en Sources: [VMware Blogs]() Topics: [GitOps](), [Platform Engineering](), [CI/CD](), [Automation](), [Cloud](), [Provisioning](), [Tooling]() Tags: [argo-cd](), [automation](), [cloud-infrastructure](), [cloud-native](), [continuous-delivery](), [deployment](), [gitops](), [home-page](), [platform](), [platform-engineering](), [provisioning](), [self-service](), [vcf-9-1](), [vcf-automation](), [vmware](), [vmware-cloud-foundation]() ### AI overview This VMware article announces VCF 9.1.1, which introduces a native GitOps service for VCF Automation Org users in Tech Preview. By integrating Argo CD, the update aims to centralize declarative application delivery, continuous delivery pipelines, and lifecycle management at enterprise scale, reducing manual work and operational friction for platform engineering teams. ### Source excerpt In today's fast-paced digital economy, where AI-driven innovation demands unprecedented agility, IT leaders are tasked with more than just provisioning infrastructure; they are expected to deliver a frictionless, self-service platform that accelerates software delivery. For platform engineers, cloud architects, and IT executives, the goal is to bridge the gap between robust infrastructure and modern application ... Continued The post From Bottleneck to Breakthrough: Centralizing GitOps at Enterprise Scale with VCF 9.1.1 appeared first on VMware Blogs. ## Introducing OttoFlow: AI Workflows for Kubernetes DevFeed: [Introducing OttoFlow: AI Workflows for Kubernetes]() Original publisher: [Read original article]() Author: Shreyas Mocherla Published: 2026-08-26T18:34:15Z Content type: release Language: en Sources: [Nirmata]() Topics: [Artificial Intelligence](), [Kubernetes](), [Platform Engineering](), [GitOps]() Tags: [agent](), [ai](), [ai-agents](), [ai-governance](), [declarative](), [gitops](), [kubernetes](), [kyverno](), [llm](), [nothing](), [platform-engineering](), [product](), [workflows]() ### AI overview Nirmata introduces OttoFlow, an open-source system for building AI workflows on Kubernetes. It represents workflows as custom resources with typed DAG steps and limits AI to selected parts of the operations process, aiming to combine deterministic, reviewable automation with model-based reasoning. ### Source excerpt AI workflows for Kubernetes, without handing an agent your kubeconfig. OttoFlow makes a workflow a custom resource: typed DAG steps, AI only where it counts. ## Nixifest: Generate Kubernetes manifests from Nix DevFeed: [Nixifest: Generate Kubernetes manifests from Nix]() Original publisher: [Read original article]() Author: bitbloxhub Published: 2026-08-21T18:33:07Z Content type: article Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [Kubernetes](), [GitOps]() Tags: [announcements](), [gitops](), [kubernetes]() ### AI overview A Nixifest project announcement and discussion describes generating typed Kubernetes manifests with Nix. The supplied evidence highlights claimed CRD support improvements over Kubenix and independence from a single GitOps solution, while later posts discuss related Nix, Terraform, container, and evaluation-performance work. ### Source excerpt LLM DISCLOSURE: I used GPT-5.6-Luna in Pi for much of the code and documentation, and GPT-5.6-Sol via ChatGPT for much of the planning and help with some architecture decisions Nixifest Nixifest Typed Kubernetes manifests generated with Nix. Better CRD support than Kubenix. Not tied to a single GitOps solution like Nixidy. 15 posts - 6 participants Read full topic ## Introducing the Remediator Agent: Turning Kyverno Policy Violations into Pull Requests, Automatically. DevFeed: [Introducing the Remediator Agent: Turning Kyverno Policy Violations into Pull Requests, Automatically.]() Original publisher: [Read original article]() Author: Akhil Chandran Published: 2026-08-14T11:29:37Z Content type: article Language: en Sources: [Nirmata]() Topics: [Kyverno](), [GitOps](), [Kubernetes](), [pull-requests](), [argocd](), [flux]() Tags: [agent](), [ai](), [argocd](), [flux](), [gitops](), [kubernetes](), [kyverno](), [other](), [pull-requests]() ### AI overview Nirmata's Remediator Agent is designed to automate remediation of Kyverno policy violations within an existing GitOps workflow. It traces violations to their Git sources, proposes deterministic or LLM-generated fixes, commits changes, opens pull requests for review, and relies on ArgoCD or Flux CD to sync approved changes back to Kubernetes. ### Source excerpt Kyverno detects Kubernetes policy violations. Nirmata's Remediator Agent turns them into reviewed pull requests within your existing GitOps workflow. ## Best Kubernetes Infrastructure as Code Tools in 2026 DevFeed: [Best Kubernetes Infrastructure as Code Tools in 2026]() Original publisher: [Read original article]() Author: Pulumi Content Team Published: 2026-08-14T00:00:00Z Content type: comparison Language: en Sources: [Pulumi]() Topics: [Infrastructure as code](), [Kubernetes](), [Terraform](), [argo-cd](), [Helm charts](), [GitOps](), [flux](), [opentofu](), [Amazon EKS](), [AWS CloudFormation](), [VPC](), [AWS IAM]() Tags: [argo-cd](), [cloudformation](), [code](), [comparisons](), [devops](), [flux](), [general](), [gitops](), [helm](), [helm-charts](), [iam](), [infrastructure](), [infrastructure-as-code](), [kubernetes](), [opentofu](), [platform-engineering](), [terraform](), [vpc]() ### AI overview This comparison explains that Kubernetes infrastructure as code spans cluster and cloud provisioning, in-cluster workload definition, and continuous delivery and reconciliation. It presents Pulumi and Terraform or OpenTofu as general-purpose provisioning options, Helm and Kustomize for workload templating, and Argo CD and Flux for GitOps reconciliation. ### Source excerpt There is no single best Kubernetes infrastructure as code tool, because "Kubernetes IaC" actually spans three different jobs. For provisioning the cluster and its cloud dependencies, Pulumi and Terraform (or OpenTofu) are the strongest general-purpose options. For templating and packaging workloads, Helm and Kustomize dominate. For continuous reconciliation once things are running, Argo CD and Flux lead the GitOps category. The right stack usually combines one tool from each layer, not a single tool that claims to do all three. What counts as infrastructure as code for Kubernetes? Kubernetes infrastructure as code work splits into three layers that get conflated constantly, and the confusion is where most tool comparisons go wrong. The cluster and cloud layer provisions the things Kubernetes itself sits on top of: the managed control plane (EKS, GKE, AKS), node pools, the VPC and subnets, IAM roles, load balancers, and cluster add-ons. Terraform, Pulumi, and cloud-native tools like CloudFormation operate here. The in-cluster workload layer defines what runs on the cluster once it exists: Deployments, Services, ConfigMaps, CustomResourceDefinitions, and the Helm charts or Kustomize overlays that template them. This is where Helm, Kustomize, and Crossplane's custom resources live. The delivery and reconciliation layer keeps what's declared in Git in sync with what's actually running on the cluster, continuously, rather than as a one-shot apply. Argo CD and Flux own this layer, and they consume the output of the other two rather than replacing them. Most real Kubernetes platforms use tools from at least two of these layers together. A team might provision EKS with Terraform, package its application with Helm, and let Argo CD reconcile it continuously. Knowing which layer a tool actually addresses, rather than treating "Kubernetes IaC" as one shopping list, is the first decision that matters. Pulumi provisions the cluster and the workloads on it in the same language Pul ## Q2 2026 Product Update: Harness Continuous Delivery & GitOps DevFeed: [Q2 2026 Product Update: Harness Continuous Delivery & GitOps]() Original publisher: [Read original article]() Author: Vishal Vishwaroop Published: 2026-08-06T00:00:00Z Content type: release Language: en Sources: [Harness Blog]() Topics: [CI/CD](), [GitOps](), [Deployment](), [Kubernetes](), [AI Agent](), [Cloud Run]() Tags: [2026](), [agent](), [cloud-run](), [continuous-delivery](), [deployment](), [gitops](), [kubernetes](), [product]() ### AI overview Harness reviews its Q2 2026 product updates, covering 38 enhancements across Continuous Delivery, Verification, and GitOps. The update includes progressive Kubernetes canary rollouts, native AI agent deployments, staged Cloud Run traffic, enhanced verification controls, and GitOps rollback and RBAC improvements. ### Source excerpt Progressive canary rollouts, native AI agent deployments, staged Cloud Run traffic, smarter verification controls, and 12 GitOps improvements -- Q2 2026 in revie | Blog ## Mastering PostgreSQL Configuration Management with CloudNativePG (CNPG) DevFeed: [Mastering PostgreSQL Configuration Management with CloudNativePG (CNPG)]() Original publisher: [Read original article]() Author: Wellingtone Luvonga Published: 2026-08-04T05:00:38Z Content type: tutorial Language: en Sources: [CYBERTEC PostgreSQL | Services & Support]() Topics: [configuration](), [PostgreSQL](), [postgresql clusters](), [Kubernetes](), [GitOps](), [YAML](), [kubectl]() Tags: [administration](), [cloudnativepg](), [configuration](), [configuration-management](), [gitops](), [how-to](), [kubectl](), [kubernetes](), [postgresql](), [replication](), [yaml]() ### AI overview This tutorial explains how CloudNativePG manages PostgreSQL configuration in Kubernetes. It contrasts imperative editing of configuration files with declarative management through Kubernetes YAML and shows how to define database parameters and pg_hba.conf rules in a CNPG cluster resource. ### Source excerpt This blog talks about Configuration Management in PostgreSQL with CNPG, with some great examples in a comprehensive way. The post Mastering PostgreSQL Configuration Management with CloudNativePG (CNPG) appeared first on CYBERTEC PostgreSQL | Services & Support. ## AI for Kubernetes: Complete Guide DevFeed: [AI for Kubernetes: Complete Guide]() Original publisher: [Read original article]() Author: Nimesha Jinarajadasa Published: 2026-07-31T03:12:00Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [Artificial Intelligence](), [Kubernetes](), [Tooling](), [Model Context Protocol](), [GitOps]() Tags: [agents](), [ai](), [clusters](), [diagnostics](), [gitops](), [guide](), [kubernetes](), [mcp]() ### AI overview A guide to AI for Kubernetes that distinguishes read-only diagnostic tools, write-capable agents, and command copilots. It explains the role of MCP, outlines the limits and risks of each category, and recommends starting with diagnosis before supervised agents and GitOps-managed workflows. ### Source excerpt The complete map of AI for Kubernetes: diagnostics, agents, and copilots, what each does today, the honest limits, and where to start. ## Using ArgoCD to Manage AI Model Deployments with GitOps DevFeed: [Using ArgoCD to Manage AI Model Deployments with GitOps]() Original publisher: [Read original article]() Author: Pramodh Kumar M Published: 2026-07-28T18:24:57Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [GitOps](), [argocd](), [model-deployment](), [Artificial Intelligence](), [model-serving](), [Architecture & Design]() Tags: [ai](), [ai-models](), [argo-rollouts-model-promotion](), [argocd](), [argocd-ai-model-deployment](), [argocd-applicationset](), [argocd-sync-waves](), [automation](), [ci-cd](), [declarative-model-serving](), [deployment](), [devops](), [gitops](), [gitops-for-ai-model-deployments](), [gitops-mlops](), [kserve](), [kserve-canary-deployment](), [kubernetes](), [kubernetes-model-deployment-rollback](), [ml-model-deployment](), [ml-model-versioning](), [mlops](), [model-deployment](), [model-registry-to-git-automation](), [model-serving](), [pull-requests](), [standard](), [tutorial]() ### AI overview This tutorial explains how to use ArgoCD and GitOps to deploy AI models while accounting for model weights stored outside container images. It covers pinned model references, rollback and recovery, synchronization ordering, readiness probes, evaluation-based promotion gates, and KServe status handling. ### Source excerpt Your microservices deploy through pull requests with full audit trails. Your models deploy because someone ran a script. Here is how to close that gap with ArgoCD, and what changes when the artifact weighs four gigabytes. ## Harness Database DevOps: Reference Data Rollbacks DevFeed: [Harness Database DevOps: Reference Data Rollbacks]() Original publisher: [Read original article]() Author: Animesh Pathak Stephen Atwell Published: 2026-07-28T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [data](), [Databases](), [Git](), [CI/CD](), [Deployment](), [CSV](), [GitOps](), [pull-requests]() Tags: [ci-cd](), [data](), [database](), [deployment](), [devops](), [files](), [gitops](), [how-to](), [pull-requests]() ### AI overview This tutorial explains how to manage database reference data with Liquibase OSS and Harness Database DevOps. It recommends storing versioned CSV files in Git, applying them with loadUpdateData, and deploying previous versions to support safer rollbacks across environments. ### Source excerpt Learn to version reference data with Liquibase OSS, automate deployments in Harness Database DevOps, and enable safe rollbacks. | Blog ## GitOps architecture, patterns and anti-patterns DevFeed: [GitOps architecture, patterns and anti-patterns]() Original publisher: [Read original article]() Author: Artem Lajko Published: 2026-07-23T05:40:01Z Content type: tutorial Language: en Sources: [Platform Engineering Blog]() Topics: [GitOps](), [Architecture & Design](), [Platform Engineering](), [CI/CD](), [Security]() Tags: [gitops](), [patterns](), [reconciliation](), [security]() ### AI overview A guide to designing GitOps for production, covering declarative and versioned configuration, pull-based deployment, continuous reconciliation, multi-cluster operation, and common anti-patterns. ### Source excerpt A platform engineer's guide to production GitOps architecture. Master advanced patterns, multi-cluster strategies, security, and avoid critical anti-patterns for scale ## A Step-by-Step Guide to Feature Flag Implementation in CI/CD DevFeed: [A Step-by-Step Guide to Feature Flag Implementation in CI/CD]() Original publisher: [Read original article]() Author: Aaron Newcomb Published: 2026-07-23T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [CI/CD](), [feature flags](), [GitOps](), [Automation](), [Microservices](), [Deployment]() Tags: [automation](), [ci-cd](), [deployment](), [feature-flags](), [gitops](), [governance](), [guide](), [microservices](), [pipelines](), [policy-as-code](), [rollback]() ### AI overview A step-by-step tutorial on implementing feature flags in enterprise CI/CD pipelines. It explains how governance, policy as code, GitOps workflows, automation, verification, gradual rollouts, and rollback capabilities can help teams manage releases across many services while maintaining control and compliance. ### Source excerpt Discover how to implement Feature Flags in CI/CD pipelines using governance, automation, and AI-driven delivery. Speed up your releases while keeping them safe. | Blog ## Orchestration powered by Temporal at Zscaler: Wrap, don't rewrite DevFeed: [Orchestration powered by Temporal at Zscaler: Wrap, don't rewrite]() Original publisher: [Read original article]() Author: Abhishek Mitra Published: 2026-07-22T00:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [Orchestration](), [Automation](), [Ansible](), [opentofu](), [Terraform](), [argocd](), [GitOps](), [Provisioning]() Tags: [ansible](), [automation](), [aws-cloudformation](), [bash](), [ci](), [cli](), [gitops](), [infrastructure-as-code](), [orchestration](), [provisioning](), [temporal-voices]() ### AI overview The article describes how Zscaler designed a durable orchestration contract above eight heterogeneous automation engines, including Ansible, Terraform, OpenTofu, Helm, ArgoCD, Crossplane, Kubernetes Cluster API, AWS CloudFormation, and Jenkins. The approach aims to coordinate existing tools without rewriting them. ### Source excerpt How one durable contract above eight automation engines changed Zscaler's architecture without changing the engines ## Harness AI Verification and Rollback for Argo CD: Limitations of Static Thresholds DevFeed: [Harness AI Verification and Rollback for Argo CD: Limitations of Static Thresholds]() Original publisher: [Read original article]() Author: Prasad Satam Akshit Madan Shubhendu Patidar Published: 2026-06-17T00:00:00Z Content type: opinion Language: en Sources: [Harness Blog]() Topics: [argo-cd](), [GitOps](), [Kubernetes](), [Artificial Intelligence](), [Prometheus]() Tags: [ai](), [argo-cd](), [gitops](), [harness](), [kubernetes](), [machine-learning](), [maintenance](), [progressive-delivery](), [prometheus](), [rollback](), [software-delivery](), [statistical-significance]() ### AI overview This vendor commentary argues that Argo Rollouts Analysis Templates can be difficult to maintain because they rely on manually defined static thresholds. It presents Harness AI Verification and Rollback as a context-aware alternative that uses unsupervised machine learning and service health trajectories to assess deviations and support rollbacks. ### Source excerpt Stop the maintenance nightmare of static thresholds. Learn how Harness AI Verification and Rollback provides context-aware safety for Argo CD. | Blog ## Faster than the advisory DevFeed: [Faster than the advisory]() Original publisher: [Read original article]() Published: 2026-06-10T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Security](), [argo-cd](), [GitOps](), [Vulnerabilities](), [Kubernetes](), [chainguard os](), [anthropic](), [Artificial Intelligence]() Tags: [ai](), [anthropic](), [argo-cd](), [chainguard-containers](), [chainguard-os](), [container-images](), [gitops](), [kubernetes](), [scanner-advisories](), [security](), [vulnerabilities](), [wolfi]() ### AI overview The article explains how Chainguard Factory delivered a patched Argo CD version to Wolfi and Chainguard OS before the related security advisory reached GitHub's global advisory database. It argues that automated upstream tracking and rapid remediation are increasingly important because vulnerability exploitation and AI-assisted discovery are outpacing traditional disclosure timelines. ### Source excerpt Chainguard often ships security fixes before advisories reach scanners. Learn why upstream speed matters in the era of AI-driven exploits. ## Azure Deployment Strategies & CI/CD Best Practices DevFeed: [Azure Deployment Strategies & CI/CD Best Practices]() Original publisher: [Read original article]() Author: Chinmay Gaikwad Published: 2026-06-09T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [Azure](), [Deployment](), [CI/CD](), [feature flags](), [GitOps](), [Infrastructure as code](), [observability]() Tags: [aks](), [azure](), [best-practices](), [ci](), [ci-cd](), [deployment](), [deployment-strategies](), [feature-flags](), [gitops](), [harness](), [iac](), [observability](), [progressive-delivery]() ### AI overview This guide explains Azure deployment strategies and CI/CD practices for safer software delivery. It covers canary, blue-green, and rolling deployments, feature flags, GitOps, infrastructure as code, pipeline controls, and observability-driven rollback, including examples involving AKS and other Azure workloads. ### Source excerpt Master Azure deployment with CI/CD, canary releases, feature flags, GitOps, and IaC. Learn how progressive delivery and Harness help teams ship faster, safer, and with fewer incidents. | Blog ## Future of IaC: Continuous Governance Through a Control Plane DevFeed: [Future of IaC: Continuous Governance Through a Control Plane]() Original publisher: [Read original article]() Author: Mrinalini Sugosh Published: 2026-06-09T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [Platform Engineering](), [Infrastructure as code](), [cloud-infrastructure](), [Provisioning](), [Terraform](), [GitOps](), [CI/CD]() Tags: [ci-cd](), [cloud](), [cloud-infrastructure](), [configuration](), [gitops](), [iac](), [infrastructure](), [platform-engineering](), [policy](), [provisioning](), [self-service](), [terraform]() ### AI overview This article explains why platform engineering teams are moving beyond point-in-time infrastructure provisioning toward continuous governance through infrastructure control planes. It focuses on reducing drift, enforcing policy, coordinating configuration and operational changes, and enabling safer self-service workflows. ### Source excerpt Learn how platform engineering teams use infrastructure control planes to reduce drift, enforce governance, and scale self-service safely. | Blog ## From Tickets to Pull Requests: Running Cilium in a GitOps Platform DevFeed: [From Tickets to Pull Requests: Running Cilium in a GitOps Platform]() Original publisher: [Read original article]() Author: Dean Lewis Published: 2026-06-02T12:56:19Z Content type: tutorial Language: en Sources: [Isovalent - The latest articles covering eBPF-based Networking, Observability, and Security]() Topics: [Cilium](), [GitOps](), [argo-cd](), [Kyverno](), [ci]() Tags: [argo](), [argo-cd](), [ci](), [cilium](), [gitops](), [hubble-timescape](), [kyverno](), [network-policy](), [platform-engineering](), [pull-requests]() ### AI overview The article describes running Cilium as part of a GitOps platform using Argo CD, Kyverno, and isopolicy CI. ### Source excerpt Run Cilium as a GitOps platform: use Argo CD, Kyverno, and isopolicy CI. ## How Microsoft is governing thousands of Kubernetes clusters without manual intervention DevFeed: [How Microsoft is governing thousands of Kubernetes clusters without manual intervention]() Original publisher: [Read original article]() Author: Adrian Bridgwater Published: 2026-05-07T22:07:21Z Content type: article Language: en Sources: [Kubernetes Overview, News and Trends | The New Stack]() Topics: [Kubernetes](), [Microsoft](), [GitOps](), [Artificial Intelligence](), [Inference](), [observability]() Tags: [ai](), [cloud-native-ecosystem](), [declarative](), [gitops](), [inference](), [kubecon-cloudnativecon-eu-2026](), [kubernetes](), [kubernetes-clusters](), [microsoft](), [observability](), [platform-engineering](), [podcast](), [post](), [sponsor-microsoft](), [sponsored-post](), [video]() ### AI overview The article examines how Microsoft addresses the operational challenges of governing thousands of Kubernetes clusters across on-premises, cloud, and edge environments. It describes limitations of single-cluster GitOps assumptions, including multi-cluster routing, secret synchronization, and unified observability, especially as distributed AI inference workloads increase. ### Source excerpt Kubernetes is complicated; everybody knows it. Logically enough, Kubernetes deployed as a cluster of collected and coalesced instances at "fleet The post How Microsoft is governing thousands of Kubernetes clusters without manual intervention appeared first on The New Stack. ## Securely troubleshoot Kubernetes clusters with Claude Code and MCP DevFeed: [Securely troubleshoot Kubernetes clusters with Claude Code and MCP]() Original publisher: [Read original article]() Published: 2026-04-13T13:05:11Z Content type: tutorial Language: en Sources: [Learn on Tailscale]() Topics: [Kubernetes](), [Model Context Protocol](), [Claude Code](), [MCP Server](), [Authorization](), [observability]() Tags: [access-control](), [claude-code](), [cli](), [codex](), [commands](), [cursor](), [gitops](), [helm-charts](), [kubernetes](), [mcp](), [observability](), [opentelemetry]() ### AI overview A practical guide to connecting Claude Code and other MCP-compatible clients to Kubernetes through an MCP server. It compares server implementations and explains operational safeguards including RBAC scoping, context pinning, observability, non-destructive mode, and secrets masking. ### Source excerpt Set up Kubernetes MCP for Claude Code, Cursor, Codex fast, and see how to handle credentials, access control, and audit trails. [Next page]()