Menu

Long-Lived Infrastructure, GitOps, and Rolling Updates (2026): How Each Layer Rolls and Which Stack to Use
📰

Long-Lived Infrastructure, GitOps, and Rolling Updates (2026): How Each Layer Rolls and Which Stack to Use

DEV Community: kubernetes·Noah Grinstein·about 7 hours ago
#ripuxIN3
#devtokubernetes#devto#dev#argo#kubernetes
Reading 0:00
15s threshold

No single tool manages long-lived infrastructure, GitOps workflows, and rolling updates equally well, so most teams combine an infrastructure tool (Terraform or OpenTofu through a plan-and-apply platform, or Crossplane), a GitOps controller (Argo CD or Flux), and a rollout tool (Kubernetes rolling updates, Argo Rollouts, or Flagger). The right stack depends on whether your long-lived infrastructure is mostly cloud resources reviewed by plan, or Kubernetes-native resources reconciled continuously. The phrase “rolling update” itself means two different things depending on the layer: rolling out a new application version across pods, and rolling updates of the infrastructure itself, such as Kubernetes cluster upgrades, node pool replacements, VM fleet refreshes, and database major-version migrations.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.