Last checked and updated on 10 Jun 2026
What Is New in Ansible 11.0
Ansible 11.0 ships with ansible-core 2.18 and introduces support for Python 3.12 on the controller while dropping Python 3.9 support. It adds new collections, removes some older ones, and brings hundreds of module updates and improvements across cloud, networking, storage, and general collections.
| Category | Key Changes |
|---|---|
| ansible-core | Python 3.12 support added, Python 3.9 dropped on controller, various bug fixes and performance improvements. |
| Added Collections | community.postgresql (3.0.0), dellemc.unity (2.0.0), ibm.spectrum_virtualize (2.0.0), and several others. |
| Removed Collections | community.azure, community.k8s (functionality moved to kubernetes.core), community.okd. |
| New Modules / Plugins | Many new modules in community.general, community.vmware, amazon.aws, cisco, fortinet, and dellemc collections. |
| Improvements | Enhanced error handling, updated cloud API support, better inventory plugins, and improved documentation across collections. |
| Deprecations | Several legacy module aliases and parameters in community collections, preparation for future Python and collection cleanups. |
Python version support updated
Ansible 11.0 adds official support for Python 3.12 on the control node and removes support for Python 3.9 on the controller.
This keeps Ansible current with the Python release schedule and enables use of newer language features and performance gains.
In practice, most modern control nodes will benefit from this change with minimal migration effort.
Collection additions and removals
New collections added to Ansible 11.0 include community.postgresql, dellemc.unity, and ibm.spectrum_virtualize.
community.azure, community.k8s, and community.okd have been removed from the bundled package. Kubernetes-related functionality is now consolidated in kubernetes.core.
You can still install removed collections manually via ansible-galaxy if your playbooks depend on them.
community.general receives extensive updates
community.general continues to be one of the most active collections with many new modules, bug fixes, and parameter improvements for system administration tasks.
Several older modules have received deprecation notices for legacy parameters to encourage cleaner playbook usage.
This collection remains essential for a wide range of common automation scenarios.
Cloud provider collections stay up to date
amazon.aws and community.aws include new modules and fixes for recent AWS service changes and API updates.
Other cloud collections such as azure (now external) and VMware receive targeted enhancements for newer features and better error reporting.
These updates help keep your cloud automation playbooks reliable with evolving provider APIs.
Networking, storage, and virtualization improvements
Cisco, Juniper, Arista, and Fortinet collections add support for newer device firmware and configuration options.
Storage collections like dellemc and purestorage expand module coverage for modern hardware capabilities.
community.vmware adds new modules and refines existing ones for vSphere management tasks.
General stability and usability enhancements
Ansible 11.0 brings improved error messages, better inventory plugin behavior, and numerous bug fixes across the included collections.
Deprecated features from earlier releases continue to be cleaned up where appropriate.
The release emphasizes reliability and compatibility with current infrastructure tools and platforms.
FAQ
Do I need to upgrade Python when moving to Ansible 11.0?
Yes on the control node if you are still using Python 3.9. Python 3.12 is now supported while Python 3.9 support has been dropped for the controller.
What happened to the kubernetes and azure collections?
community.k8s and community.azure have been removed from the bundled package. Use kubernetes.core for Kubernetes work and install community.azure manually if still needed.
Are there major breaking changes in Ansible 11.0?
No major breaking changes in core behavior. The primary impacts are Python version updates, collection removals, and ongoing deprecations.
Can I still use collections that were removed in 11.0?
Yes. Removed collections can be installed separately using ansible-galaxy collection install.
What is the main benefit of upgrading to Ansible 11.0?
Newer Python support, updated modules for current cloud, network, and storage platforms, and overall stability improvements across the Ansible package.