integrate Kustomize into kubectl

[Liujingfang1]

Feature Description

• One-line feature description (can be used as a release note): add kustomize subcommand into kubectl
• Primary contact (assignee): Liujingfang1, monopole
• Responsible SIGs: sig-cli
• Design proposal link (community repo): Kustomize subcommand integration
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: pwittrock, soltysh
• Approver (likely from SIG/area to which feature belongs): pwittrock, soltysh
• Feature target (which target equals to which milestone): 1.14
  • Stable release target (x.y) 1.14

Kustomize has been developed in its own repo kubernetes-sigs/kustomize for the past few months. It has been iterated for several versions and is in good shape now. This feature is to enable kustomize in kubectl.

[Liujingfang1]

/sig cli

[Liujingfang1]

/area kubectl
/kind feature

[Liujingfang1]

cc @soltysh @pwittrock @seans3 @juanvallejo

[Liujingfang1]

/cc @monopole

[Liujingfang1]

/tracked yes

[kacole2]

@Liujingfang1 please also tag any PRs within k/k here as well to track progress

[Liujingfang1]

The PR for this change kubernetes/kubernetes#70213

[AishSundar]

@Liujingfang1 is this feature entering alpha in 1.13? is the above PR the only one needed? It seems quite size-able to be included in a short 'stability' focussed release, especially past enhancement freeze. Please file an exception with details around why this has to go in this release vs waiting for the next release, what risk could we be introducing adding a huge feature at this point, exiting tests and confidence on the feature stability. We can have further discussions on the exception email. Thanks.

[Liujingfang1]

@AishSundar Since Kustomize has been well developed in its own repo. If we enable it in kubectl, it can be GA in 1.13. The above PR is the only PR needed. I'll file an exception. Thank you.

[juanvallejo]

@Liujingfang1 Thanks for opening this. I think there's a few items to resolve as part of adding this feature to kubectl:

• I agree with @smarterclayton 's comment here that we should come up with a name that fits in with existing commands under the kubectl command tree.
• I also think we should discuss how Kustomize as a whole will co-exist with existing commands with regards to user experience, etc.

We could start by opening a PR updating the KEP with more details describing the user flow of this feature as a kubectl command, and have some of these discussions in that thread

[kacole2]

/milestone v1.13
/stage stable