2024.1 Series Release Notes

18.0.0

New Features

  • Add Cilium as a supported network driver of Kubernetes

  • Add a feature to prevent drivers clashing when multiple drivers are able to provide the same functionality.

    Drivers used to be selected based on a tuple of (server_type, os, coe). This can be a problem if multiple drivers provide the same functionality, e.g. a tuple like (vm, ubuntu, kubernetes).

    To allow for this, it is now possible to explicitly specify a driver name, instead of relying on the lookup. The driver name is the same as the entrypoint name, and can be specified by a Cluster Template through the Glance image property “magnum_driver”.

Upgrade Notes

  • Support for deploying Calico v3.3 has been dropped.

  • k8s_fedora_atomic_v1 driver has been dropped.

  • k8s_coreos_v1 driver has been dropped.

  • k8s_fedora_ironic_v1 driver has been dropped.

  • Tiller support has been dropped, following labels are not functional anymore: * tiller_enabled * tiller_tag * tiller_namespace

  • Dropped swarm drivers, Docker Swarm is not supported in Magnum anymore.

  • The Magnum service enable the API policies (RBAC) new defaults and scope by default. The Default value of config options [oslo_policy] enforce_scope and [oslo_policy] enforce_new_defaults have been changed to True.

    This means if you are using a system scope token to access Magnum API then the request will fail with a 403 error code. Also, new defaults will be enforced by default. To know about the new defaults of each policy rule, refer to the Policy New Defaults Sample File.

    If you want to disable them then modify the below config options value in magnum.conf file:

    [oslo_policy]
enforce_new_defaults=False
enforce_scope=False

  • The registry for cloud-provider-openstack has been updated from docker.io/k8scloudprovider to registry.k8s.io/provider-os/.

Deprecation Notes

  • Remove support for cluster upgrades with the Heat driver. The Heat driver can longer support cluster upgrades due to these being unreliable and untested. The action now returns an HTTP 500 error. A Cluster API driver provides a way forward for Magnum to support this api action again for Kubernetes. In the meantime blue/green deployments, where a replacement cluster is created, remain a viable alternative to cluster upgrades.

Critical Issues

  • Magnum Core Team has historically limit changing of defaults in labels. This is because existing Cluster Templates in a deployment falls back to using the defaults in code if a specific label is not specified. If defaults change, an existing deployment’s Cluster Templates may stop working after a Magnum upgrade.

    Magnum will now no longer keep image tag labels (e.g. cloud_provider_tag, flannel_tag) static. Please specify explicitly all image tags for the images your Cluster Templates will be using, to prevent a future change breaking your Cluster Templates. Refer to the documentation under ‘Supported Labels’ for a list of labels Magnum is tested with.