kPow requires at least one configured Kafka cluster to operate.
When configuring Multi-Cluster installations the first cluster configured is your Primary Cluster and contains all the snapshot, metrics, and audit metadata for the installation.
Each configured Kafka cluster can have one associated Schema registry and/or Kafka connect cluster.
kPow is compatible with Apache Kafka 1.0+.
kPow has been tested and is compatible with Apache Kafka, Amazon MSK, Red Had AMQ Streams, Aiven Managed Kafka, Instaclustr Managed Kafka, Confluent Platform and Confluent Cloud*, Azure Event Hubs*, Redpanda*.
*Some disk related metrics and telemetry are not available when using kPow with Confluent Cloud, Azure Event Hubs or Redpanda.
kPow is capable of integrating with FIPS compliant Kafka clusters.
Contact [email protected] for assistance.
User permissions to Kafka cluster resources are defined by Cluster actions.
kPow connects to a Kafka cluster with exactly the same configuration as a Kafka consumer or producer.
This configuration may be familiar to you, and is provided to kPow by environment variables.
The list of connection variables follows, many are optional. Consult the Kafka client docs for more info.
Optional, UI friendly label for this cluster and resources
The Kafka cluster bootstrap URL
Optional, set to
Optional, set to
PLAINTEXT, SSL, SASL_PLAINTEXT, or SASL_SSL
GSSAPI, AUTHBEARER, SCRAM, PLAIN,
Java Authentication and Authorization Service config
The path to a keystore for auth with certificates
The password to access the auth keystore
The password of the key within the keystore
The file format of the keystore file
The key manager algorithm used for SSL
The path to a truststore for auth with certificates
The password to access the auth truststore
The file format of the truststore file
The trust manager algorithm user for SSL
Often required when authenticating via SSL
Name of the security provider used for SSL
A list of cipher suites
TLS, TLSv1.1, or TLSv1.2
The list of protocols enabled for SSL