Current Series Release Notes¶
22.0.0.0rc1-43¶
New Features¶
Administrators can now hide a cluster template to prevent users from creating new clusters with it. Hidden templates are invisible to non-admin users — fetching one returns 404 and using it in a cluster create request returns 403. This is particularly useful for retiring a template that still has active clusters: instead of waiting for all those clusters to be deleted (which would be required before the template can be removed), administrators can simply hide it so no new clusters are created while existing ones continue to operate normally.
Upgrade Notes¶
k8s_fedora_coreos_v1driver (also known asHeat-baseddriver) has been dropped following earlier deprecation.
Support for legacy admin service-user credentials in the
[keystone_authtoken]configuration section has been removed. The deprecatedadmin_user,admin_password, andadmin_tenant_nameoptions were dropped from keystonemiddleware in the 2026.2 release. Operators must ensure that service-user credentials are configured in the[keystone_auth]section using the keystoneauth1 password auth plugin options (auth_url,username,password,project_name, etc.). Magnum will no longer fall back to[keystone_authtoken]for admin authentication and will raise an error if[keystone_auth]is not properly configured.
The deprecated
auth_urioption in[keystone_authtoken]is no longer recognised by Magnum. This option was removed from keystonemiddleware in the 2026.2 release. Operators should usewww_authenticate_uriin[keystone_authtoken]instead. Note thatauth_urlin[keystone_auth]is now the primary source for the Keystone endpoint used by Magnum’s service-user session.
TLS session options (
certfile,keyfile,cafile,insecure,timeout) are no longer accepted in the[keystone_authtoken]section as deprecated aliases for the[keystone_auth]equivalents. These options must be set directly in[keystone_auth]if required.
Keystone trust manager functionality has been dropped (Heat-based driver was the only user - and it has been removed).
Bug Fixes¶
The boot_volume_size label value is passed as a string from the API. The validator now converts it to an integer before comparison.