Configure Ansible Playbooks for Confluent Platform

To configure custom properties for Confluent Platform components, set the properties in the Ansible inventory file, hosts.yml.

In the example below, the initLimit and syncLimit properties are set in the ZooKeeper properties file, the property gets set in the Kafka properties file, and the confluent.controlcenter.ksql.default.advertised.url property gets set in the Confluent Control Center properties file. Note that default in the confluent.controlcenter.ksql.default.advertised.url property value is the name Control Center should use to identify the ksqlDB cluster.

        initLimit: 6
        syncLimit: 3
      properties: 15
        confluent.controlcenter.ksql.default.advertised.url: http://ksql-external-dns:1234,http://ksql-external-dns:2345

Set custom properties on a specific host

You can configure a particular host with unique properties. Put the component properties block directly under the host.

In the example below, the broker.rack property is set to us-west-2a for the host,

          broker.rack: us-west-2a

Additional configuration properties

This section describes a few additional Ansible configuration properties.

JMX Exporter

JMX Exporter is disabled by default. When enabled, the JMX Exporter jar is pulled from the Internet and enabled on the broker only. Enable JMX Exporter on your Kafka brokers , as shown below:

jmxexporter_enabled: true

Confluent Server or Kafka

Confluent Server is the default version deployed with Confluent Platform. To install Kafka instead, set the following property in the all group in the hosts.yml file.

confluent_server_enabled: false

Configure Schema Validation

You can configure Schema Validation in your Kafka brokers when running Confluent Server. Set the following properties in the all group in the hosts.yml file.

confluent_server_enabled: true
kafka_broker_schema_validation_enabled: true

This feature is not supported for Kafka.