Handling of new CRDs

[benkeil]

Could we add a flag to say the command should not fail if the old crd (in the cluster in my case) does not exist?

[everettraven]

@benkeil Thanks for filing the issue. Would you mind elaborating a bit more on the use case for this so that I can better understand how the functionality might be used?

[benkeil]

For a developer platform I want to implement a workflow where platform providing teams need to submit their CRDs via a PR in a central repository. If the CRD they provide is new it would be nice if the CLI command would not return an error (maybe via flag) so I don’t need to write a bash workaround. I want to compare an file from the PR with what the cluster knows.
Theoretically the CRD is valid because it does not hurt any rules.