TLS, Kafka, and ZooKeeper Configuration

The Humio Operator supports TLS configuration for LogScale pods, additional Kafka settings, and ZooKeeper SSL configuration.

Configuring TLS with the Operator

By default, TLS is enabled on each LogScale pod. This is recommended, however, in some cases you may want TLS to be disabled. To do this, use the following configuration.

If TLS is enabled here, TLS must also be enabled for the Kafka connection. If TLS on the LogScale pods is disabled but the Kafka connection should use SSL, configure Kafka explicitly to use SSL.

yaml
spec:
  tls:
    enabled: false

Additional Kafka configuration with the Operator

Extra Kafka configs can be set and used by the LogScale pods. This is mainly used to toggle TLS when communicating with Kafka. To enable TLS, for example, set the following configuration.

SSL is enabled by default when using TLS for the LogScale pods. See Configuring TLS with the Operator.

yaml
spec:
  extraKafkaConfigs: "security.protocol=SSL"

ZooKeeper deployment in Kubernetes and the Operator

When TLS is enabled for LogScale, TLS is by default also enabled for connections to ZooKeeper. In some cases, such as with MSK, TLS will be enabled for the Kafka brokers but not for ZooKeeper. To disable TLS for ZooKeeper, set the following in values for the HUMIO_OPTS environment variable: -Dzookeeper.client.secure=false.