How would you use GitOps to manage Kubernetes cluster lifecycles?
This tests cluster lifecycle GitOps, not just app delivery. A strong answer uses Flux plus Cluster API on a hub cluster, stores cluster definitions in Git, and rolls upgrades via MachineDeployments.
This tests extending GitOps from app delivery to infrastructure, treating cluster creation, upgrades, and decommissioning as declarative state. A strong answer describes a management cluster running Flux that watches a Git repo with Cluster API manifests, machine templates, and bootstrap configs; it provisions workload clusters, handles version bumps via rolling MachineDeployment updates, and manages day-two addons with HelmRelease or Kustomization.
Read the original → fluxcd.io
- #gitops
- #kubernetes
- #cluster-api
- #infrastructure-as-code
- #flux
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.