2025.2 Series Release Notes

21.0.1-8

Bug Fixes

  • Creating or updating a cluster template with an image that does not have the os_distro property set previously failed with a confusing « cluster type not supported » error listing unrelated driver combinations. This case is now detected explicitly and raises a clear error stating that the image’s os_distro is unset and therefore not supported.

  • The boot_volume_size label value is passed as a string from the API. The validator now converts it to an integer before comparison.

Other Notes

  • The error raised when a cluster’s (server_type, os, coe) combination does not match any loaded cluster driver now lists the combinations that are actually supported by the loaded drivers, making it easier to diagnose why a driver could not be matched. A separate, more specific error is now raised when a matching driver exists but is a beta driver that has not been enabled via [drivers]/enabled_beta_drivers.

21.0.0

Nouvelles fonctionnalités

  • Add a validation for the case when boot_volume_size label and flavor’s disk are both zero.

  • Add subject key identifier extension to x509 operations signing function. Allows for magnum Kubernetes clusters to generate certificates with authority key identifier extension.

  • This release introduces the “credentials” endpoint to Magnum API which initially supports rotation of cluster credentials. The definition of « credential » and the implementation to perform the rotation, is dictated by the underlying driver.

Notes dépréciées

  • The “magnum-api-wsgi” wsgi entrypoint has been deprecated will be removed in a future release. This is due to changes in Python packaging. Operators using the “magnum-api-wsgi” should migrate away from it. See the OpenStack goverance page for more info.

Other Notes

  • Test jobs for testing cluster creation using Heat driver have been removed, following deprecation in 2025.1 release.

  • Container publish jobs for images used in Heat driver have been removed, following deprecation in 2025.1 release.

  • When debug logging is enabled, periodic update logging will now output Cluster UUID instead of database ID to better identify the object being updated.