This follows the cluster inventory API release process, albeit without the automation and the image releases.
This release proposal follows a lazy consensus model: the proposal is approved unless an OWNER objects within two weeks of this issue being opened. Silence is treated as approval.
Changes since the last release (v0.4.1)
The main purpose of this release is to make the v1beta1 CRDs and client available for downstreams. v1alpha1 is still provided, so downstreams are not required to migrate to v1beta1 if they upgrade to this release.
Known issues
None.
This follows the cluster inventory API release process, albeit without the automation and the image releases.
This release proposal follows a lazy consensus model: the proposal is approved unless an OWNER objects within two weeks of this issue being opened. Silence is treated as approval.
Changes since the last release (v0.4.1)
The main purpose of this release is to make the v1beta1 CRDs and client available for downstreams. v1alpha1 is still provided, so downstreams are not required to migrate to v1beta1 if they upgrade to this release.
Known issues
None.