feat: bump up CRD version to v1beta1

[binbin-li]

Description

What this PR does / why we need it:

Update CRD version from v1alpha1 to v1beta1.

Basically I followed this example, API conversion guide and this example to make the upgrade. For the hub-spoke conversion code, I use conversion-gen to auto-generate it.

Added a doc listing the steps of the upgrade.

Steps for the upgrade:

1. Create new APIs version by: kubebuilder create api --group config.ratify.deislabs.io --version v1beta1 --kind <kind>
2. Copy over existing types.
3. Create an unversioned API which will become the hub between v1alpha1 and v1beta1 to faciliate conversion. When we add a new V1 version, it would be convenient to generate conversion functions between v1 and unversioned.
4. Copy over existing types to unversioned API.
5. In each "spoke" version package(v1alpha1, v1beta1), add marker +k8s:conversion-gen directive pointing to the “hub” version package. It must be in doc.go.
6. In “spoke” version package, add a localSchemeBuilder = runtime.NewSchemeBuilder(SchemeBuilder.AddToScheme) in groupversion_info.go so the auto-generated code would compile.
7. In unversioned package, create doc.go file and add marker: +kubebuilder:object:generate=true
8. Add +kubebuilder:skip to unversioned api.
9. Mark v1beta1 as the storage version, add marker +kubebuilder:storageversion to v1beta1.
10. run make manifests generate to generate CRD objects, DeepCopy and conversion methods.

Notes:
in this pr, we didn't make any changes to the CRD properties. In the future, if we have incompatible changes, we would have to Add {kind}_conversion.go in each version to implement Convertible for each type.

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):

Fixes #602

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Test passed. Tested locally with v1alpha1 CR as well.

Checklist:

• Does the affected code have corresponding tests?
• Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
• Does this introduce breaking changes that would require an announcement or bumping the major version?
• Do all new files have appropriate license header?

[codecov]

Codecov Report

Patch coverage: 41.66% and no project coverage change

Comparison is base (7cf6951) 44.51% compared to head (c3e6fad) 44.51%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #664   +/-   ##
=======================================
  Coverage   44.51%   44.51%           
=======================================
  Files          56       56           
  Lines        3266     3266           
=======================================
  Hits         1454     1454           
  Misses       1664     1664           
  Partials      148      148           

Impacted Files	Coverage Δ
pkg/controllers/certificatestore_controller.go	12.50% <25.00%> (ø)
pkg/controllers/store_controller.go	35.59% <50.00%> (ø)
pkg/controllers/verifier_controller.go	37.09% <50.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[sozercan]

instead of this being a breaking change, you should consider creating a seperate v1beta1 api and converting between different versions https://book.kubebuilder.io/multiversion-tutorial/tutorial.html
example: eraser-dev/eraser#544

[susanshi]

thanks for the PR binbin. Left some questions

[sozercan]

i don't see usage of unversioned. if it's not a specific Kubernetes API reference, you should use unversioned API

[binbin-li]

Actually in controller, the Store object is retrieved from K8s Cluster which should be a valid version. https://github.com/deislabs/ratify/blob/main/pkg/controllers/store_controller.go#L64
So I use the v1beta1 version across the controller file, for other files we should definitely use unversioned API but there is no usage yet.
And for this specific function, we could probably do a manual conversion from v1beta1 to unversioned once we retrieved object from the cluster.