image-automation-controller/api/v1beta1
Michael Bridgen 5b9631327f Graduate v1alpha2 API to v1beta1
This does the following:

 - copies the type definitions from v1alpha2 to v1beta1
 - changes the "stored" version to v1beta1
 - gives the CRD a conversion strategy of None, meaning just rewrite the version
 - switches the controller to use v1beta1
 - moves the generated documentation to v1beta1

This effectively rebadges the v1alpha2 version of this part of the
image API to v1beta1. The v1alpha2 version is left in place; there are
no conversion issues, as with v1alpha1->v1alpha2. The CRD specifies
that converting between v1alpha2 and v1beta1 just means changing the
version (i.e., the schema and semantics are the same).

Signed-off-by: Michael Bridgen <michael@weave.works>
2021-06-28 11:26:59 +01:00
..
doc.go Graduate v1alpha2 API to v1beta1 2021-06-28 11:26:59 +01:00
git.go Graduate v1alpha2 API to v1beta1 2021-06-28 11:26:59 +01:00
groupversion_info.go Graduate v1alpha2 API to v1beta1 2021-06-28 11:26:59 +01:00
imageupdateautomation_types.go Graduate v1alpha2 API to v1beta1 2021-06-28 11:26:59 +01:00
reference.go Graduate v1alpha2 API to v1beta1 2021-06-28 11:26:59 +01:00
zz_generated.deepcopy.go Graduate v1alpha2 API to v1beta1 2021-06-28 11:26:59 +01:00