Delivery for Kubernetess
Kubernetes delivery is how applications are packaged and released to a cluster. Helm packages manifests into versioned charts with configurable values, Kustomize patches plain YAML for each environment, and GitOps tools such as Argo CD or Flux keep the cluster in sync with manifests stored in Git.
Stage: Operations · Part of the Kubernetes roadmap · Last reviewed 19 November 2026
What to learn in Delivery
- Install, upgrade and roll back a release with Helm
- Override chart values per environment using values files
- Use Kustomize bases and overlays to vary manifests without templates
- Explain the pull based GitOps model and how drift is detected and corrected
- Describe a pipeline that builds an image and updates a manifest in Git
Delivery interview questions
What is the difference between Helm and Kustomize?
Helm uses Go templates and a values file to generate manifests, and tracks releases with history and rollback. Kustomize needs no templating, and instead applies patches and overlays to base YAML. Many teams use one or combine them, depending on how much parameterisation they need.
What does GitOps mean in practice?
Git holds the desired state of the cluster, and an in-cluster agent such as Argo CD or Flux continuously compares it with the live state and applies differences. Changes happen through pull requests, which gives review history and easy rollback by reverting a commit.
Where Delivery fits in the Kubernetes roadmap
Delivery belongs to the Operations stage (advanced level), which takes about 22 hours. Scale and release.
Other units in this stage
Back to the full Kubernetes roadmap