Release 88.2: Flink Consumers and Encrypted Configuration

Toggle dark mode

Release Info

Kpow can be found on Dockerhub

docker pull operatr/kpow:88.2

View our Docker quick start guide for help getting started.

Kpow can be found on ArtifactHub

Helm version: 1.0.31

helm repo add kpow https://charts.kpow.io
helm repo update
helm install --namespace factorhouse --create-namespace my-kpow kpow/kpow --version 1.0.31 \
--set env.LICENSE_ID="00000000-0000-0000-0000-000000000001" \
--set env.LICENSE_CODE="KPOW_CREDIT" \
--set env.LICENSEE="Your Corp\, Inc." \
--set env.LICENSE_EXPIRY="2024-01-01" \
--set env.LICENSE_SIGNATURE="638......A51" \
--set env.BOOTSTRAP="127.0.0.1:9092\,127.0.0.1:9093\,127.0.0.1:9094" \
--set env.SECURITY_PROTOCOL="SASL_PLAINTEXT" \
--set env.SASL_MECHANISM="PLAIN" \
--set env.SASL_JAAS_CONFIG="org.apache.kafka.common.security.plain.PlainLoginModule required username=\"user\" password=\"secret\";"
--set env.LICENSE_CREDITS="7"

View our Helm instructions for help getting started.

Kpow can be found on the AWS Marketplace

View our AWS Marketplace documentation for help getting started.

Kpow can be downloaded and installed as a Java JAR file. This JAR is compatible with Java versions 11+.

Download Kpow Java JAR

View our JAR quick start guide for help getting started.

Kpow can be downloaded and installed as a Java JAR file. This JAR is compatible with Java 8.

Download Kpow Java 8 JAR

View our JAR quick start guide for help getting started.

Download VPAT
Factor House publish a VPAT (Voluntary Product Accessibility Template) for each release.

For more information, read the Kpow accessibility documentation.

Kpow v88.2 introduces improved support for monitoring Flink consumers, the ability to encrypt your Kpow configuration to avoid passwords in plaintext, new configuration options for connecting to Confluent Schema Registries that require mutual TLS for authentication, and more.

Simple Consumers

Kpow provides great insight into Kafka Consumer Groups.

Until v88.2 Kpow provided little insight into the earlier implementation of Kafka consumers - Simple Consumers. That's because simple consumers have no group membership or assignment information, often the only information we have on them is a name and an understanding of their consumer offsets.

Simple consumers are often anonymous, ad-hoc, or bespoke consumption workloads that manage their own state. One prominent user of simple consumers is Flink, the popular stream processing framework.

In Kpow v88.2 we introduce a new 'Simple Consumers' tab in the Consumers UI, under this tab you will find information about any simple consumer that we can identify consuming from your cluster - including Flink workloads.

Note: If hundreds of ad-hoc or simple groups degrade your Kpow performance, turn this feature off with SNAPSHOT_SIMPLE_GROUPS=false.

Kpow Flink UI

Simple Consumer UI

Simple consumers metrics are held separately from our existing consumer group metrics as simple consumers have a different lifecycle from consumer groups. They don't have a group state and tend to exist for as long as their offsets are commit to the consumer_offsets topic. That means old/idle simple consumers can have a prolonged period where they are considered lagging - as such we don't intermingle aggregate simple and consumer group metrics.

The following simple consumer metrics have been added to Kpow's Prometheus endpoint:

  • "simple.group.offset.lag.total" - the total lag of all simple consumers
  • "simple.group.offset.delta.total" - the total read/s of all simple consumers
  • "simple.topic.consumption.inactive.mins" - the total minutes a topic has seen zero consumption by simple consumers
  • "simple.topic.offset.delta" - the total read/s of all simple consumers to a topic
  • "simple.topic.offset.lag" - the total lag of all simple consumers to a topic
  • "simple.broker.offset.delta" - the total read/s of all simple consumers to a broker
  • "simple.broker.offset.lag" - the total lag of all simple consumers to a broker

In a future release we will introduce aggregate simple consumer metrics to the Overview UI.

Kpow Encrypted Configuration

Kpow is deployed by our customers in every cloud and on premises. Often times sensitive configuration is protected by vaults or secret managers.

Kpow requires standard Kafka configuration to connect to and manage your Kafka resources, this can include plaintext passwords for keys, keystores, truststores, and even the bindPassword for LDAP if you are using our JAAS LDAP integration. Kpow v88.2 includes support for obfuscating and encrypting plaintext configuration.

For more information on how to secure Kpow configuration see the Kpow Secure Configuration Guide. Use the Java API to secure your own client configuration.

We have chosen to open-source our implementation as the kpow-secure project, available under the Apache 2.0 license.

Confluent Schema TLS Configuration

In this release we introduce support for connecting to Confluent Schema Registry with mutual TLS authentication.

The following environment variables can be used to configure registry connections with mutual TLS:

  • SCHEMA_REGISTRY_SSL_KEYSTORE_LOCATION
  • SCHEMA_REGISTRY_SSL_KEYSTORE_PASSWORD
  • SCHEMA_REGISTRY_SSL_KEY_PASSWORD
  • SCHEMA_REGISTRY_SSL_KEYSTORE_TYPE
  • SCHEMA_REGISTRY_SSL_KEYMANAGER_ALGORITHM
  • SCHEMA_REGISTRY_SSL_TRUSTSTORE_LOCATION
  • SCHEMA_REGISTRY_SSL_TRUSTSTORE_PASSWORD
  • SCHEMA_REGISTRY_SSL_TRUSTSTORE_TYPE
  • SCHEMA_REGISTRY_SSL_TRUSTMANAGER_ALGORITHM
  • SCHEMA_REGISTRY_SSL_ENDPOINT_IDENTIFICATION_ALGORITHM
  • SCHEMA_REGISTRY_SSL_PROVIDER
  • SCHEMA_REGISTRY_SSL_CIPHER_SUITES
  • SCHEMA_REGISTRY_SSL_PROTOCOL
  • SCHEMA_REGISTRY_SSL_ENABLED_PROTOCOLS
  • SCHEMA_REGISTRY_SSL_SECURE_RANDOM_IMPLEMENTATION
  • SCHEMA_REGISTRY_SSL_KEYSTORE_KEY
  • SCHEMA_REGISTRY_SSL_KEYSTORE_CERTIFICATE_CHAIN
  • SCHEMA_REGISTRY_SSL_TRUSTSTORE_CERTIFICATES
  • SCHEMA_REGISTRY_SSL_ENGINE_FACTORY_CLASS

Release v88.2 Changelog

See the Factor House Product Roadmap to understand current delivery priorities.

Kpow v88.2 Changelog

See the full Kpow Changelog for information on previous releases

  • Improved support for Flink / Simple consumers
  • Support for encrypted Kpow configuration
  • Support for Confluent Schema Registry w/ Mutual TLS
  • Export to CSV from the kREPL
  • Data Import improvements and bugfixes
Flex v88.2 Changelog

See the full Flex Changelog for information on previous releases

  • Introduced Simple Consumer (Flink) UI
Release 95.1: A unified experience across product, web, docs and licensing

95.1 delivers a cohesive experience across Factor House products, licensing, and brand. This release introduces our new license portal, refreshed company-wide branding, a unified Community License for Kpow and Flex, and a series of performance, accessibility, and schema-related improvements.

Release 94.6: Factor Platform, Ververica Integration, and kJQ Enhancements

The first Factor Platform release candidate is here, a major milestone toward a unified control plane for real-time data streaming technologies. This release also introduces Ververica Platform integration in Flex, plus support for Kafka Clients 4.1 / Confluent 8.0.0 and new kJQ operators for richer stream inspection.

Release 94.5: New Factor House docs, enhanced data inspection and URP & KRaft improvements

This release introduces a new unified documentation hub - Factor House Docs. It also introduces major data inspection enhancements, including comma-separated kJQ Projection expressions, in-browser search, and over 15 new kJQ transforms and functions. Further improvements include more reliable cluster monitoring with improved Under-Replicated Partition (URP) detection, support for KRaft improvements, the flexibility to configure custom serializers per-cluster, and a resolution for a key consumer group offset reset issue.

Start your streaming transformation today.

 Try both Kpow or Flex free for 30 days with a single license - no credit card required.