Release 0.15.5

This release improves lag monitoring reliability during broker degradation and adds configuration options for the lag monitor to the Backup CRD.

Installation

For new installations, see the Installation guide.

For upgrading existing installations, see the associated Upgrading to 0.15.x guide.

Improved lag monitoring

The backup process tracks how far behind it is by periodically fetching the latest offsets from the source cluster. Previously, these offset requests ran in the metrics exporter task, sharing the same Kafka connection as the main consumer and blocking the Tokio runtime while waiting for a response. Under normal conditions this works fine, but when a broker is slow or degraded, the blocking call can add latency to the consumer connection.

Offset requests now run on a dedicated connection in a separate task, so a slow broker no longer affects the main backup consumer.

As part of this change, the Backup CRD now exposes a lagMonitor field to configure the refresh interval and request timeout for offset tracking.

apiVersion: kannika.io/v1alpha
kind: Backup
metadata:
  name: my-backup
spec:
  source: "my-kafka-endpoint"
  sink: "gcs-storage"
  lagMonitor:
    refreshInterval: "15s"
    requestTimeout: "10s"

Lag Monitor Learn how to configure the backup lag monitor's refresh interval and request timeout.

Bugfixes

• Fixed custom credentials set via config.security.username and config.security.password being ignored in the API Helm chart because the basicAuth defaults always took precedence.

Release notes

For a full list of changes, see the Changelog.