When CRDs and CRs are deployed in the same apply, the apply will fail due to race condition

[dniasoff]

What would you like to be added:
I would like kubectl to optionally wait for CustomResourceDefinitions to be established before attempting to apply a Custom Resource that is dependent on it.

A suitable workflow is to just apply all CRDs, do the equivalent of ```kubectl wait --for=condition=established -f crds.yaml`` and then apply other resources

Why is this needed:
When deploying CRDs and CRs in the same apply, the apply of CRs will initially fail. Although you can then run another apply which will then work, this is messy

See kubernetes-sigs/kustomize#3502

[k8s-ci-robot]

@dniasoff: This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[eddiezane]

We've discussed this before and decided to keep kubectl unbiased on the resources it is applying.

We do have a better warning message planned though kubernetes/kubernetes#107363

/close

[k8s-ci-robot]

@eddiezane: Closing this issue.

In response to this:

We've discussed this before and decided to keep kubectl unbiased on the resources it is applying.

We do have a better warning message planned though kubernetes/kubernetes#107363

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.