OpenTofu 1.11.5 ships with upstream Go security fixes and continues a trend: infrastructure-as-code tools are becoming security products as much as automation products. Here’s what that means for platform teams.
Backstage-style portals, GitOps controllers, and IaC engines (Terraform/OpenTofu/Pulumi) are converging into repeatable platform ‘golden paths.’ Here’s a 2026 blueprint that stays modular.
OpenTelemetry adoption is running into a new bottleneck: operating collector fleets. IBM Instana just made OpAMP-powered fleet management generally available, highlighting a shift from ‘instrumentation’ to ‘collector ops’ as the next maturity step.
GitOps is great until you run a large Kubernetes fleet. Fastly describes the gaps they hit — orchestration, validation, blast-radius control — and how they layered a rollout system on top of Argo CD. Here’s what platform teams can steal.
OpenTofu’s new -json-into flag streams machine-readable events without sacrificing the human CLI UX. It’s a small UX change with big implications for CI/CD, policy checks, and developer experience.
OpenTofu’s CNCF home matters less for politics and more for operations: predictable releases, ecosystem trust, and a path to standardizing policy. Here’s a practical blueprint for running OpenTofu at scale with GitOps, drift control, and safe migration from Terraform.
GitLab’s Transcend event pitches agentic AI across the software lifecycle with governance. Here’s what’s real, what’s marketing, and what to validate in your pipeline.
Argo CD 3.3.0 ships new actions and upgrade considerations that matter most to self-managing installations—where the GitOps tool is also managed by GitOps.
Dapr’s Conversation component abstracts LLM provider differences behind a runtime API, letting teams focus on prompts and tool calls while the sidecar handles retries, auth, and provider quirks. It’s an early blueprint for agentic, ops-friendly AI integration.
Argo CD 3.3.0 sharpens the line between old apply behaviors and server-side apply. If Argo CD manages itself, upgrades can fail unless you adopt the right sync options—making this a good time to audit GitOps bootstrapping patterns.
Agentic workflows can reduce toil in pipelines and incidents, but only with clear tiers of access, provenance controls, and strong audit trails.
