Skip to content

v7.10.0

Choose a tag to compare

@mnaser mnaser released this 28 Oct 12:13

New Features

  • The libvirt chart now supports hook scripts through conf.hooks, which are placed in /etc/libvirt/hooks inside the libvirt pods. This allows operators to run custom logic on libvirt events, such as adjusting the definition of guests that are live migrated in from other hosts.
  • Administrators can quarantine an instance by replacing the security groups on its ports with an administrative security group named quarantine and locking it. Project members then can't change the security groups, allowed address pairs or port security of a quarantined port. Quarantine is disabled by default. Set neutron_policy_server_quarantine_enabled to true to enable it, which sets the Neutron update_port policy to Neutron's default rule with the quarantine check added.

Upgrade Notes

  • The Keycloak database schema is migrated automatically when the new version starts, and the migration can't be reversed. Take a backup of the Keycloak database before upgrading so that you can roll back if needed. Users need to sign in again after the upgrade.
  • Keycloak metrics are now scraped from the management interface on port 9000.
  • Tokens from an external identity provider are now exchanged with federated client authentication or the JWT authorization grant, which replace the deprecated legacy token exchange. The authentication guide describes how to set up both.
  • The community.general collection is upgraded to 11.4.9, which requires ansible-core 2.16 or later.
  • The Neutron policy server checks now run inside the Neutron API server, and the neutron-policy-server sidecar container and its port 9697 are removed. Deployments that override Neutron policy rules with http://neutron-server:9697/... checks must switch them to the address_pair, port_update, port_delete or quarantine checks before upgrading, otherwise the deployment stops with an error listing the affected rules.

Security Issues

  • Keycloak is upgraded from 24.0.5 to 26.8.1, which includes all upstream security fixes released since the previous version.

Bug Fixes

  • Strict mode on the database cluster is now relaxed and restored on every node while Keycloak is deployed, instead of only on the node that serves the connection. A mismatch between nodes could evict a database node from the cluster during a Keycloak schema migration.
  • The Keycloak clients for Alertmanager, Grafana and Prometheus are now created as confidential clients. They were previously public clients, so Keycloak ignored the client secrets that these services already use.
  • The Octavia and Manila roles now set the quotas of the admin and service projects with an included copy of the OpenStack quota module that works with older OpenStack SDK releases. This fixes deployments failing with KeyError: 'project_id' on hosts that use the OpenStack SDK package from Ubuntu 24.04.