feat(crds): Update CRDs to apiextensions.k8s.io/v1

[alexec]

Signed-off-by: Alex Collins alex_collins@intuit.com

Checklist:

• My organization is added to USERS.md.

[naor2013]

Is there a way to keep the old version still as well? Either with a helm chart that detects your k8s version automatically or simply by keeping both version and labeling the old version with "old" (for example, "namespace_install_old.yaml")?

[alexec]

Is there a way to keep the old version still as well? Either with a helm chart that detects your k8s version automatically or simply by keeping both version and labeling the old version with "old" (for example, "namespace_install_old.yaml")?

What about producing two sets of CRDs?

[naor2013]

What about producing two sets of CRDs?

That would also help, if there would be 2 versions of CRD and we could choose the "old one".

[alexec]

https://kubernetes.io/blog/2019/06/20/crd-structural-schema/

[naor2013]

@alexec what about what we wrote here before? Having two sets of CRDs to keep the old version as well?

[alexec]

Could you use the old CRDs on the release-2.12 branch?

[naor2013]

Could you use the old CRDs on the release-2.12 branch?

Now it seems like there isn’t much difference between 2.12 and 3.0 so it’s possible, but the moment you’ll change the yamls in version 3.x, it won’t be possible anymore.