Kubectl Apply 2019: Defense Against the Dark Arts
summary
Explains why kubectl apply is reworked, what was built and how it behaves now: a new server-side apply API moves diff and patch logic into the server, adds managedFields to track field owners, replaces fragile strategic merge directives, and makes dry-run accurate. On the client side a declarative customization file and generators produce configmaps/secrets with hash suffixes and update references to force rolling updates. Ongoing work covers pruning deleted resources, blocking apply on status, and pluggable generators for sealed secrets and other workflows.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:07Cluster IP fields
- 2:06Generating the patch
- 4:45Declarative application management
- 8:47Two parts of the problem
- 10:05Server Client Relationship
- 11:44Dry Run
- 13:50Config Files
- 18:05Metalevel transformations
- 26:28Questions
- 28:33QA
related talks
29mWhat's New With Kubectl and Kustomiz...
07mKustomize: Manage K8S manifests natively
38mSIG CLI Deep Dive
25mKubernetes SIG CLI: Intro and Updates
35mKubernetes SIG CLI: Intro And Updates
32mFrom User To Contributor: A Quick Guide To Kubectl & Kustomize
16mLightning Talk: Kustomize Your Operator
22mIt's Terraform All the Way Down