The inclusion of Kustomize[1] into kubectl is a big step forward for the K8s ecosystem as it provides a native solution for application configuration. Once you really grok the pattern of using overlays and patches, it starts to feel like a pattern that you'll want to use everywhere (even outside of the k8s ecosystem).
I'm excited to see that the kubectl docs[2] are actually recommending -k as the default solution (vs -f).
Though Apply can be run directly against Resource Config
files or directories using -f, it is recommended to run
Apply against a kustomization.yaml using -k. The
kustomization.yaml allows users to define configuration
that cuts across many Resources (e.g. namespace).
Really amazing work from everyone on this release.
I'm excited to see that the kubectl docs[2] are actually recommending -k as the default solution (vs -f).
Really amazing work from everyone on this release.[1]https://kustomize.io
[2]https://kubectl.docs.kubernetes.io/pages/app_management/appl...