1. Home
  2. Ansible

Prerequisites for Installing Confluent Platform with Ansible Playbooks

General requirements

  • Ansible 2.11

    Ansible Playbooks for Confluent Platform 7.2 no longer supports Ansible 2.9 as the version is end-of-life (EOL).

    Due to breaking changes in Ansible 2.13, Ansible Playbooks for Confluent Platform does not work with Ansible 2.13.

  • Python 3.6 or later on the control nodes and on the managed nodes (Confluent Platform hosts)

    Ansible Playbooks for Confluent Platform 7.2 no longer support Python 2.x, as it is EOL.

  • SSH access between Ansible control nodes and Confluent Platform hosts

    For the steps and the command to verify the SSH connections for all the hosts involved, see Prepare Ansible Inventory File to Install Confluent Platform.

  • sudo access for SSH user to all Confluent Platform hosts

    Starting in 7.1.0, Ansible Playbooks for Confluent Platform supports tag-based separation of tasks that require root permission from tasks that do not require root permission. You can run the latter tasks without root privileges. However, there are certain steps where you do need root access. For details, see Install Confluent Platform without root access.

  • (Optional) Internet connectivity to pull Confluent Platform software from packages.confluent.io. If you don’t have internet access, refer to Air-gapped Deployment of Ansible Playbooks for Confluent Platform for deploying in an air-gapped environment.

Confluent Platform version

It is highly recommended that you use the same version of Confluent Ansible playbooks as the Confluent Platform version.

Supported Operating Systems

Ansible Playbooks for Confluent Platform support the operating systems listed in the operating systems supported by Confluent Platform components, except for those marked as deprecated.

Hardware requirements

Refer to the Confluent Platform component on-premises system requirements.

Ports

Refer to the ports used by Confluent Platform components.

Users

Each Confluent Platform component runs under its own user set up during installation. The usernames are prefixed with cp- followed by the component name. For example, cp-kafka and cp-schema-registry. The one exception is that ZooKeeper runs as the cp-kafka user.

Time synchronization

Clock synchronization on each Kafka broker is required to ensure the full system functions correctly. See Time synchronization requirement for details.