Update apiVersion

[grampelberg]

I've gone through and updated all the apiVersions. While doing it, I realized that it is probably valuable to version each of these apis differently (so that it isn't quite a big of a bang to push the version forward). This suggests that idea that each major API has its own namespace and can version independently.

[alban]

Thanks! I will update smi-adapter-istio to pick up the new name once this is merged.

There was a discussion to change v1beta1 to v1alpha1. Do we keep the "beta" names in the end?

[grampelberg]

@alban I don't have a preference on v1beta1 vs v1alpha1, what do you think?

[alban]

@grampelberg I would start with v1alpha1 since we are not yet at the point of providing instructions for migration between different versions of the API:

https://kubernetes.io/docs/concepts/overview/kubernetes-api/#api-versioning

Alpha level:
The API may change in incompatible ways in a later software release without notice.
Beta level:
The schema and/or semantics of objects may change in incompatible ways in a subsequent beta or stable release. When this happens, we will provide instructions for migrating to the next version.

[grampelberg]

@alban great call. I'll merge for now, as always if anyone has issues we can get them fixed in a follow up PR.