Kurrent Docs
Skip to main content

Kurrent Cloud
Spin up a managed instance of KurrentDB and start building in minutes. Available in AWS, Azure and GCP.
Sign up for freeDocumentation

Welcome to the KurrentDB Kubernetes Operator guide. In this guide, we’ll refer to the KurrentDB Kubernetes Operator simply as “the Operator.” Use the Operator to simplify backup, scaling, and upgrades of KurrentDB clusters on Kubernetes.

Important

The Operator is an Enterprise-only feature, please contact us for more information.

Why run KurrentDB on Kubernetes?

Kubernetes is the modern enterprise standard for deploying containerized applications at scale. The Operator streamlines deployment and management of KurrentDB clusters.

Features

  • Deploy single-node or multi-node clusters
  • Back up and restore clusters
  • Automate backups with a schedule and retention policies
  • Perform rolling upgrades and update configurations

New in 1.4.0

  • Support configurable traffic strategies for each of server-server and client-server traffic. This enables the use of LetsEncrypt certificates without creating Ingresses, for example. See Traffic Strategies for details.
  • Support backup scheduling and retention policies. There is a new KurrentDBBackupSchedule CRD with a CronJob-like syntax. There are also two mechanisms for configuring retention policies: a .keep count on KurrentDBBackupSchedule, and a new .ttl on KurrentDBBackup.
  • Support standalone read-only replicas pointed at a remote cluster. This enables advanced topologies like a having your quorum nodes in one region and a read-only replica in a distant region. See Deploying Standalone Read-Only Replicas for an example.
  • Support template strings in some extra metadata for child resources of the KurrentDB object. This allows, for example, to annotate each of the automatically created LoadBalancers with unique external-dns annotations. See KurrentDBExtraMetadataSpec for details.

New in 1.4.1

  • Fix rolling restarts to be quorum-aware for extra data safety.
  • Add quorum-aware full restarts for changes that must be applied to all nodes at once, like adding TLS.
  • Fix the internodeTrafficStrategy: SplitDNS setting to run correctly on more container runtimes.
  • Fix a hang caused adding to pod labels in extraMetadata after a KurrentDB was deployed.
  • Correctly enforce the immutability of the sourceBackup setting to prevent confusing behavior.
  • Fix the helm chart to prevent allowing two operator instances to briefly conflict during upgrades.

Supported KurrentDB Versions

The Operator supports running the following major versions of KurrentDB:

  • v25.x
  • v24.x
  • v23.10+

Supported Hardware Architectures

The Operator is packaged for the following hardware architectures:

  • x86_64
  • arm64

Technical Support

For support questions, please contact us.

First Steps

Ready to install? Head over to the installation section.

Last Updated