Hello, This is a summary of the Magnum PTG sessions that we had on Monday (EMEA+US slot, attendance: 12) and Tuesday (EMEA+APAC slot, attendance: 4) Driver Guidance and Strategy Driver Landscape: The community present on the sessions continues to state that Magnum should act as a wrapper for third-party drivers rather than having an "official" internal one (to be state, currently there’s the Heat based driver that is deprecated and subject to removal) Driver Comparison: magnum-cluster-api (MCAPI): Actively supported and developed by Vexxhost. magnum-capi-helm: No activity since Dec 2025 with majority of the core team behind it inactive. Long-term Goal: The community intends to work towards having bothmagnum-capi-helm andmagnum-cluster-apirunning both drivers simultaneously on a single installation, to allow migration and to allow users to explore both drivers. Project Health and Maintenance Developer Support: While the team is small, at least two organizations are actively supporting the project. New reviewers are being onboarded (Rico Lin@VexxHost is one of the volunteers). Communication: The team agreed to hold a regular meeting at 13:00 UTC (every two weeks). Community will be also present on Kubernetes Slack (channel #openstack-magnum) in addition to #openstack-containers on OFTC to increase community reach. User Feedback: A question regarding driver usage will be added to the next OpenStack User Survey to better understand the deployer landscape. Technical Infrastructure and CI CI Improvements: There is a strong push to implement Zuul based CI for both drivers. Resource Allocation: The team will experiment with ubuntu-noble-32GB labels in Zuul (which support nested virtualization) to run Devstack (with devstack-plugin-container) and Sonobuoy smoke tests. Eventlet Migration: Work is underway to migrate away from Eventlet, but progress depends on getting the CI stable enough to validate the changes. Removing Tech Debt: There is also work underway to remove years of tech debt in usage of deprecated Oslo libraries functions and other similar methods/libraries API and Image Management Microversions: Discussion focused on using microversions for Magnum API versioning and API extensions to replace the existing labels that are being used. Image Publishing: To simplify deployments, the project will point users toward Vexxhost’s capo-image-elements for building and obtaining cluster images. Driver Pain Points magnum-capi-helm: Issues were noted regarding "blind spots" during status reporting (clusters getting stuck without feedback), lack of support for unique nodegroup labels, and risks associated with cluster upgrades across incompatible templates. With the lack of activity in that driver’s code space - the community will need to reassess if the driver can continue under the project’s governance. Security & Architecture: magnum-cluster-api issues with direct communication between magnum-conductor and workload clusters has been raised (and the overall documented architecture - both network and security wise). There is some documentation in OpenStack Ansible (OSA) that could be used as a starting point of that documentation efforts in magnum-core and/or magnum-cluster-api. There is also potential in future rework of magnum-cluster-api proxy architecture utilizing Cluster API runtime SDKs and remote tunnels instead. Thank you for all attendees, for additional content please see the etherpad [1]. [1]: https://etherpad.opendev.org/p/apr2026-ptg-magnum Cheers, Michal