Are Your Declarative Configurations Human Friendly? Closer Look at Code Reviews with GitOps
summary
Helm templating and Kustomize overlays hide real resource changes: a Grafana upgrade from 6.3.0 to 6.16.2 produces 50 differences only visible after running helm template and a diff tool; dyff fails when document counts change. A new CLI called Importer replaces marked sections by pulling literal fragments from source files (example: Argo CD 2.1.0 → 2.1.2 shows extra manifest vars), making commits fully declarative but requiring automation to avoid stale generated code. Tools mentioned: dyff and Helm templates.
AI-written summary · about
chapters (4)
- 0:00Start
- 0:10Are Your Declarative Configurations Human Friendly? Closer Look at Code Reviews with Gitops
- 11:03Code Review with Helm Because Helm is a package manager, it allows easy integration with third party dependencies
- 11:27Code Review with Kustomize Kustomize allows templating and easy override and most of the configuration is intuitive But not for the reviewer perspective - it can be difficult to track created resources from the automation to diff based on customize build
related talks
29mHow to Preview and Diff Your Argo CD Deployments
34mKustomize vs Helm - Civil War
19mThe Art of GitOps: Rendered Manifests
27mDay 2 Operations of Helm Charts
47mDevOps:Config Mgmt for Kubernetes workloads with GitOps and Helm
28mReconciling ClickOps and GitOps
09mThe thin line between code and configuration (YAML/Helm rant)
28mThe Building Blocks of DX: K8s Evolution From CLI to GitOps
