RFC: Which style should the CLI follow? (kubectl -k or standalone)

[bittner]

kustomize-wrapper is meant to be a very thin, almost unnoticeable integration layer of Python and kustomize. Convenience features should come in where it makes sense (installing, running integrated tools).

This makes sense to not irritate or confuse users who know kustomize already.

Different styles already out there

Interestingly, there are already 2 types of "kustomize" CLI implementations out there:

• Integrated in kubectl (e.g. kubectl kustomize builds/shows, kubectl apply -k applies a configuration)
• Standalone (e.g. kustomize shows usage, kustomize build builds/shows a configuration)

With the current CLI implementation kustomize-wrapper leans towards the kustomize CLI that is integrated into kubectl. But is this really a good idea? Which style should our CLI follow?

Cc @srueg