Release v0.10.0-alpha.0 #1995
mdbooth
announced in
Announcements
Release v0.10.0-alpha.0
#1995
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Breaking API Changes
v0.10.0 is a major update which brings major changes to the API.
v1alpha5 is no longer served
If you are still using v1alpha5, this will not work in v0.10.0. However, for this release only objects are still defined in the CRDs and the code is still present, so as a temporary workaround it is possible to manually edit the CRDs to set versions.served to true for v1alpha5 objects. This is not tested, and we have low confidence that this will work without problems. Some manual effort may be required to check and fix automatically converted objects.
v1alpha6 and v1alpha7 are deprecated
v1alpha6 and v1alpha7 objects will be automatically converted to v1beta during use. This is well tested. We don’t anticipate problems with these conversions.
We will stop serving and testing v1alpha6 in the next release, and v1alpha7 some time after that. You should update to use v1beta1 natively as soon as possible.
v1beta1 is released
v1beta1 marks a major update to the CAPO API. The specific changes from v1alpha7 are documented here: https://cluster-api-openstack.sigs.k8s.io/topics/crd-changes/v1alpha7-to-v1beta1
More than this, though, it marks an intention by the maintainers to stop making breaking changes. The API will continue to evolve, but we will make every effort to do this without introducing more backwards-incompatible changes.
Management cluster changes
Removal of MutatingWebhookConfiguration
CAPO no longer uses a mutating webhook, and its configuration is removed. If you upgrade your management cluster with clusterctl this will be handled correctly. If you do it manually you must ensure you remove the MutatingWebhookConfiguration
capo-mutating-webhook-configuration. If you do not you may see errors like the one in #1927.Minimum management cluster version is now 1.25
v0.10.0 now uses https://kubernetes.io/docs/reference/using-api/cel/ for some API validations, which only became available without a feature gate in 1.25. Consequently we now require the management cluster to be at least k8s 1.25.
Highlighted new features
API Reference documentation
We now automatically publish API reference documentation! The documentation for v1beta1 can be found here: https://cluster-api-openstack.sigs.k8s.io/api/v1beta1/api
Floating IP IPAM Provider
It is now possible to allocate floating IPs for individual machines using the new Floating IP IPAM Provider documented here: https://cluster-api-openstack.sigs.k8s.io/api/v1alpha1/api#infrastructure.cluster.x-k8s.io/v1alpha1.OpenStackFloatingIPPool
Attach them to a machine via the new floatingIPPoolRef in OpenStackMachineSpec: https://cluster-api-openstack.sigs.k8s.io/api/v1beta1/api#infrastructure.cluster.x-k8s.io/v1beta1.OpenStackMachineSpec
Detailed changes
flatcar-sysexttemplate to use regular Flatcar images by @tormath1 in ✨ Addflatcar-sysexttemplate to use regular Flatcar images #1776spec.allowAllInClusterTraffictospec.ManagedSecurityGroupsby @EmilienM in ✨ Movespec.allowAllInClusterTraffictospec.ManagedSecurityGroups#1892IdentityRef.Kindby @EmilienM in 🐛 RemoveIdentityRef.Kind#1903allocation_poolsfor subnet by @dulek in ✨ Add support to setallocation_poolsfor subnet #1847v1alpha8tov1beta1by @EmilienM in 🌱 Renamev1alpha8tov1beta1#1902New Contributors
Full Changelog: v0.9.0...v0.10.0-alpha.0
This discussion was created from the release Release v0.10.0-alpha.0.
Beta Was this translation helpful? Give feedback.
All reactions