Skip to content

    Announcing the 0.11.0 Release

    This new release introduces Backup Worker Groups to spread the backup workload across multiple pods, and adds topic metadata to the console.

    Installation

    For new installations, see the Installation guide.

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

    Spread your backup workload with Worker Groups

    The new Backup Worker Groups feature allows you to spread the backup workload across multiple pods. This can be useful when you have a large number of topics in a Backup and want to avoid overloading a Pod. Using multiple Pods also allows to spread the backup workload across multiple nodes.

    Worker Groups
    Configure worker groups in the console

    This feature requires a minimum Kubernetes version of 1.28 to work, as it relies on the apps.kubernetes.io/pod-index label introduced in that version.

    A new workGroup field has been added to the Backup specification to accommodate this feature:

    Backup
    apiVersion: kannika.io/v1alpha1
    kind: Backup
    metadata:
    name: big-backup
    spec:
    source: "kafka"
    sink: "storage"
    workGroup:
    workers: 3
    seed: 123 # Optional

    Backups are now StatefulSets

    To accommodate the new Backup Worker Groups feature, A Backup will now be deployed using a StatefulSet instead of a Deployment .

    Upgrading to this version will automatically migrate existing Backups to use StatefulSets.

    View topic metadata in the console

    The console will now show more metadata for topics like the amount of partitions, compaction, and retention settings.

    Topic Metadata
    View metadata when adding topics to a Backup
    Restore Topic
    View metadata when restoring topics

    Topics matched by topic selectors

    When using topic selectors, the console will show which topics are matched by which topic selector.

    Matched topic selectors tooltip
    Matched topic selectors tooltip

    Other changes

    • Added labels to all child resources to link them to their parent

    • The ingestion rate is now also shown per topic in the backup details in the console

    • Extra resource requirements validation in the console verifying that the request is not higher than the limit

    • Added tooltips in the console where applicable

    Breaking changes

    Bug fixes

    • General: Fix backup jobs not being able to resume if a gap in offsets is detected.

    • Console: Fix platform info error icon being clipped when the side menu is collapsed

    • API: Fix regex topic selector when filtering topics

    • Helm: Fixed the Custom Resource Definitions (CRDs) not being packaged in the kannika-crd chart

    Upcoming features

    Some features that we are working on include:

    • Restore preflight checks: We’re enhancing the console with new preflight checks for restores. These checks will proactively identify potential issues before you initiate the restore process, helping you avoid unexpected errors.
    • Integrated schema mapping in the console: We are adding schema mapping to the console, which will work on top of the current Kubernetes-based schema mapping process.

    Please check the Roadmap for more information on upcoming features.

    Release Notes

    For a full list of changes, see the Changelog.