Confluent Operator 1.6.2 Release Notes

This topic summarizes the technical details of Confluent Operator 1.6.2 release.

Notable fixes

  • The init container uses the same resource requests/limits as specified for a component container.
  • When configuring static host-based routing for external access to Kafka, only one Ingress Controller is now needed.
  • It is now configurable whether Confluent Operator will check for DNS resolution success before scaling up brokers. The check is disabled by default.
  • When internal network encryption (internalTLS=true) is enabled, communication among MDSs happens over the internal Kubernetes network, and no longer over the external network.
  • Confluent Operator pod can be configured for High Availability through setting pod replicas to 2 or more.