Ansible Playbooks for Confluent Platform Release Notes

Ansible Playbooks for Confluent Platform (Confluent Ansible) is continuously updated with new features and enhancements. This topic highlights the significant new and updated features, enhancements, bug fixes, and known limitations in each release.

Note

For the list of security and vulnerability issues fixed in any release, see Security Advisories and Security Release Notes.

June 23, 2026 Confluent Ansible 8.1.4 Release Notes

Ansible Playbooks for Confluent Platform (Confluent Ansible) 8.1.4 allows you to deploy Confluent Platform version 8.1.4.

Breaking changes

There are no breaking changes in this release.

New features

Adds the capability to generate a support bundle for Confluent Ansible playbook runs. See Support bundle.

Enhancements

  • Adds validation of Confluent Platform package availability before installation. The playbook now fails early if the requested package version is not available in the configured repositories, before removing the existing packages.

  • Introduces a Confluent CLI v3.0.0 preflight assertion.

Bug fixes

  • Fixed an issue that caused the Kafka broker and Kafka controller to restart twice.

  • Fixed the issue with the security.properties copy task that failed to copy the file to the Ansible host.

  • Fixed kafka-storage format failures on KRaft clusters with secrets protection enabled. The master key is now passed to the format step using the CONFLUENT_SECURITY_MASTER_KEY environment variable. See Control master key regeneration.

  • Fixed custom certificate chain building for multi-tier and partial-chain PKI setups. Chains now assemble correctly for root and intermediate bundles, and for DoD-style partial chains.

Known limitations

There are no known limitations in this release.

Deprecations

There are no deprecations in this release.

Ansible Playbooks for Confluent Platform 8.1.2 Release Notes

Ansible Playbooks for Confluent Platform (Confluent Ansible) 8.1.2 allows you to deploy Confluent Platform version 8.1.2.

This release supports Ansible versions 9.x to 11.x and Python versions 3.10+. The recommended Ansible version is 11.x.

New features and enhancements

Confluent Ansible now supports using AWS Systems Manager (SSM) to establish connections to managed nodes.

Notable fixes

  • Fixed an issue where pipefail caused failures when extracting distinguished names from keystores in mTLS setups.

  • For the list of security and vulnerability issues fixed in this release, see Security Advisories and Security Release Notes.

Ansible Playbooks for Confluent Platform 8.1.1 Release Notes

Ansible Playbooks for Confluent Platform (Confluent Ansible) 8.1.1 allows you to deploy Confluent Platform version 8.1.1.

This release supports Ansible versions 9.x to 11.x and Python versions 3.10+. The recommended Ansible versions are 11.x.

Fixed Issues

  • Enhanced security by masking potentially exposed sensitive secrets.

  • Fixed idempotency on configuration files when using the secrets protection feature.

  • Added ability to override a list of loggers using the update_log4j task in the common role.

  • Made retries and delays in health checks configurable for users.

  • Introduced indexing and default rollover strategy for Log4j 2 file.

  • Fixed the failures in rolling deployments of connectors when mTLS was enabled and a key store and trust store were provided.

  • ZooKeeper-based Kafka cluster on Just a Bunch of Disks (JBOD) can use the migration playbook to move to KRaft.

  • Replaced the deprecated apt-key add command with modern APT key management commands.

  • For the list of security and vulnerability issues fixed in this release, see Security Advisories and Security Release Notes.

Ansible Playbooks for Confluent Platform 8.1.0 Release Notes

Ansible Playbooks for Confluent Platform (Confluent Ansible) 8.1.0 allows you to deploy Confluent Platform version 8.1.0.

This release supports Ansible versions 9.x to 11.x and Python versions 3.10+. The recommended Ansible versions are 11.x.

New features

Confluent Unified Stream Manager Agent Support

You can use Confluent Ansible to deploy Unified Stream Manager.

See Configure and Deploy Unified Stream Manager using Confluent Ansible.

Unified Stream Manager Schema Registry Support

You can use Confluent Ansible to perform Schema Registry switchover from Confluent Platform to Confluent Cloud.

See Schema Registry Switchover using Confluent Ansible and Unified Stream Manager.

Notable enhancements

  • Kafka brokers now use node_id, by default, instead of broker_id.

    To use the legacy broker_id: Set enable_node_id: false in your inventory file.

  • Added configurations to enable Jolokia Access Control.

Fixed Issues

  • Removed Confluent Metrics Reporter configuration from the Kafka broker and KRaft controller.

  • Fixed the Prometheus/Alertmanager health checks for Control Center.

  • Fixed an issue when enabling the systemd service for Control Center archive installations.

  • For the list of security and vulnerability issues fixed in this release, see Security Advisories and Security Release Notes.