Comment 4 for bug 1921553

Hi Ken,
The current multi-version support was a quick win, and it just simply try to parse the spec using the current latest version(in this case, it's v1) then retry using v1beta1 if it was failed.
As you have already figured out, you will be able to use v1beta1 if the spec has some v1beta1 specific fields(like the top-level `validation`). It is probably the workaround to solve the issue.
More accurate multi-version support is definitely a good feature to implement in the future.

As Cory mentioned, any versions of resources will be all converted to the latest version after deployed to the k8s side. And as far as I know, the k8s list/delete/get operations actually ignores the API versions.
I don't think it will have any issues when the upstream service tries to list these CRDs.