Last checked and updated on 30 May 2026
What Is New in Ansible 14
Ansible 14 ships with ansible-core 2.21 and brings important modernization, expanded database support, Kubernetes/Helm updates, and collection cleanups that affect daily playbook maintenance and operational reliability.
| Category | Highlights |
|---|---|
| New Features | PostgreSQL support in community.proxysql (new pgsql_* modules), Helm v4 compatibility across kubernetes.core modules, new Cisco resource modules (e.g. ios_bfd_interfaces), community.clickhouse and other collections added |
| Improvements | ansible-core git submodule handling, extensive community.general CmdRunner migrations and Python 3.7+ cleanups, kubernetes.core check_mode and ownership improvements, network device enhancements |
| Breaking Changes | community.dns drops support for ansible-core < 2.17 and Python < 3.8, dnspython < 2.0.0 removed |
| Deprecations | hetzner.hcloud datacenter_info server_types return value |
What Python and dependency changes were made in Ansible 14?
The most visible shift is a continued push toward modern Python. community.dns is now Python 3 only, dropping ansible-core versions before 2.17 and Python versions below 3.8. It also removes support for dnspython older than 2.0.0.
In practice, this aligns with broader ecosystem trends. Many modules across community.general and other collections received Python 3.7 idiom updates, f-string conversions, and CmdRunner migrations for more reliable command execution and locale-independent parsing.
# Example impact on inventory or DNS playbooks
- name: Update DNS record
community.dns.nameserver_record_info:
# modules now require Python 3.8+
...
Most teams running on supported controller Python versions will see no disruption, but test environments still on older Python will need upgrades.
How has Kubernetes and Helm support improved in Ansible 14?
Yes, kubernetes.core 6.4.0 brings significant Helm v4 compatibility fixes across helm_info, helm_plugin, helm_pull, helm_repository and related modules. New options like plain_http for registry auth and check_mode support in k8s_drain were added.
This matters if you manage Helm releases or drain nodes in production. The take_ownership behavior during initial Helm installs was also fixed, allowing better adoption of existing resources without workarounds.
Watch out for Helm v4-specific changes in your CI pipelines — test thoroughly before rolling out.
What new database and proxy capabilities does Ansible 14 introduce?
community.proxysql 1.8.0 adds full PostgreSQL support with six new modules: proxysql_pgsql_users, proxysql_pgsql_servers, proxysql_pgsql_hostgroup_attributes, proxysql_pgsql_query_rules, proxysql_pgsql_query_rules_fast_routing, and proxysql_pgsql_replication_hostgroups.
This is a major win for teams running hybrid MySQL/PostgreSQL ProxySQL setups. Combined with community.postgresql and community.mysql updates (e.g. MAINTAIN privilege support), database automation is broader and more consistent.
Which collections were added, removed, or significantly updated?
Ansible 14 removed awx.awx, cisco.dnac, and junipernetworks.junos from the bundled package (still installable manually). New additions include community.clickhouse, graphiant.naas, and pcg.alpaca_operator.
Network collections saw steady updates — new BFD modules in cisco.ios, expanded RouterOS support, and Meraki Umbrella/SASE enhancements. community.general continues its massive modernization with hundreds of cleanups.
Most production playbooks will require minimal changes unless you depended on the removed collections.
Are there important breaking changes or deprecations to watch for in Ansible 14?
The primary breaking change is in community.dns around Python and ansible-core minimum versions. hetzner.hcloud deprecated the server_types return value in datacenter_info in favor of more granular location data.
ansible-core improved git submodule tracking to respect .gitmodules or remote HEAD instead of hardcoding master. This fixes long-standing issues but may surprise playbooks that relied on the old behavior.
In practice, run ansible-playbook --syntax-check and test in staging. The porting guide will be your best reference once 14.0.0 is released.
Common Questions about Ansible 14
Does upgrading to Ansible 14 require changes to existing playbooks?
Most playbooks will continue to work unchanged unless you rely on community.dns with older Python or the removed collections.
What happened to community.dns support in Ansible 14?
It now requires ansible-core 2.17+ and Python 3.8+, with dnspython >= 2.0.0.
Are there new ProxySQL modules for PostgreSQL in Ansible 14?
Yes, community.proxysql now includes proxysql_pgsql_users, proxysql_pgsql_servers and related modules for full PostgreSQL support.
How does kubernetes.core handle Helm v4 in Ansible 14?
Multiple helm_* modules were updated for Helm v4 compatibility and k8s_drain gained check_mode support.
Were any collections removed from the Ansible 14 package?
awx.awx, cisco.dnac and junipernetworks.junos are no longer bundled but can be installed separately with ansible-galaxy.
What core improvement affects git submodules in Ansible 14?
The git module now uses the branch from .gitmodules or remote HEAD instead of hardcoding master when track_submodules=yes.