What Is New in Ansible 13.0
Ansible 13.0 ships with ansible-core 2.20 and brings Python 3.14 support along with the removal of older Python versions on controller and targets. It also includes two new collections, removes two others, and delivers hundreds of updates across networking, cloud, storage, and virtualization collections.
| Category | Key Changes |
|---|---|
| ansible-core | Python 3.14 support added, Python 3.11 dropped on controller, Python 3.8 dropped on targets. |
| Added Collections | hitachivantara.vspone_object (1.0.0), ravendb.ravendb (1.0.4). |
| Removed Collections | community.digitalocean, ibm.qradar. |
| New Modules / Plugins | community.general.ip2location_info, community.general.sssd_info, community.proxmox.proxmox_ceph_* modules, numerous fortinet.fortimanager modules, podman inventory plugins and system connection modules. |
| Breaking / Deprecations | Many community.aws module aliases deprecated in favor of shorter names or amazon.aws equivalents, community.general module_utils becoming private, several community.general modules scheduled for removal. |
| Collection Updates | Significant updates in community.vmware, community.docker (5.0.1), community.general (12.0.1), dellemc.openmanage (iDRAC10 support), fortinet.fortimanager, purestorage collections, and many others. |
Python version requirements have changed
Ansible 13.0 adds official support for Python 3.14 on the controller while dropping Python 3.11 support for the controller and Python 3.8 on managed targets.
This aligns with the upstream Python release cycle and prepares the ecosystem for newer language features.
In practice, most users on modern Linux distributions will not notice any disruption, but older environments may need Python upgrades before upgrading Ansible.
Collection changes expand and clean the package
Two new collections join the Ansible package: hitachivantara.vspone_object for Hitachi VSP One Object storage and ravendb.ravendb for RavenDB management.
community.digitalocean and ibm.qradar have been removed from the bundled package. You can still install them manually with ansible-galaxy if needed.
This keeps the default distribution focused while allowing users to add specialized collections as required.
community.aws modules receive major deprecation cleanup
Many legacy aliases in community.aws (such as aws_eks_cluster, aws_s3_bucket_info, aws_kms) are now deprecated in favor of clearer names under community.aws or amazon.aws.
WAF Classic modules are also deprecated following AWS retirement plans.
In practice, update your playbooks to the new module names soon to avoid warnings and future removal.
Kubernetes and Helm handling sees refinements
In kubernetes.core, the status.values return value in helm and helm_info modules is deprecated in favor of status.release_values.
Sensitive information in kubeconfig is now selectively redacted for better security in output.
These changes improve consistency when working with Helm releases and protect credentials in logs or debug output.
community.general and community.proxmox add useful new modules
New modules include ip2location_info for IP geolocation lookups and sssd_info for checking SSSD domain status via D-Bus.
community.proxmox adds dedicated Ceph MDS, Mgr, and Mon management modules plus proxmox_sendkey for sending key presses to VM consoles.
These additions make common infrastructure and monitoring tasks easier without custom scripting.
Networking and storage collections continue steady evolution
community.routeros adds extensive support for new RouterOS 7.x paths and parameters.
fortinet.fortimanager receives dozens of new modules for modern FortiManager features.
purestorage.flasharray and flashblade collections improve info gathering, policy handling, and error resilience.
netapp collections fix idempotency issues and expand support for newer storage features.
FAQ
Do I need to upgrade Python when moving to Ansible 13.0?
Yes for the controller if you were still on Python 3.11. Targets should move away from Python 3.8. Python 3.14 is now supported on the controller.
Are the removed collections still usable?
Yes. community.digitalocean and ibm.qradar are no longer included by default but can be installed manually using ansible-galaxy collection install.
What should I do about the deprecated community.aws aliases?
Replace them with the recommended shorter names (e.g., use community.aws.eks_cluster instead of the old aws_eks_cluster alias) to eliminate deprecation warnings.
Is community.general still safe to use after module_utils changes?
Yes for normal playbook and role usage. The module_utils and doc fragments are becoming private in community.general 13.0, so custom code that imports them may need updates or discussion with maintainers.
Are there any major breaking changes in Ansible 13.0?
No major breaking changes in core behavior. The main impacts are Python version drops, collection removals, and deprecations that were previously announced.