You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor: rebrand to Kafka Backup Operator and change CRD API group
Per Strimzi maintainer feedback (discussion #8750), change the CRD API
group from backup.strimzi.io to kafkabackup.com to avoid implying
official Strimzi/CNCF affiliation or colliding with a future official
Strimzi backup project.
- API group: backup.strimzi.io -> kafkabackup.com
- Project name: "Strimzi Backup Operator" -> "Kafka Backup Operator for Strimzi"
- Add non-affiliation disclaimer to README and Helm chart
- Rename Helm chart directory and all template helpers
- Update Cargo package/binary name, Dockerfile, Makefile, CI workflows
- Regenerate CRD YAMLs with new group
- strimzi.io/cluster label intentionally kept (Strimzi convention)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
A Strimzi-native Kubernetes operator for **Strimzi backup**and disaster recovery of Apache Kafka clusters. Provides dedicated CRDs for automated Kafka backup scheduling, point-in-time recovery, and multi-cloud storage — fully integrated with the Strimzi ecosystem.
7
+
> **Disclaimer:**This project is not part of the [Strimzi](https://strimzi.io/) project or the CNCF. It is an independent, community-built operator designed to work with Strimzi-managed Kafka clusters.
8
8
9
-
## Why Strimzi Backup?
9
+
A Kubernetes operator for **Kafka backup** and disaster recovery of Strimzi-managed Apache Kafka clusters. Provides dedicated CRDs for automated Kafka backup scheduling, point-in-time recovery, and multi-cloud storage — designed for the Strimzi ecosystem.
10
+
11
+
## Why Kafka Backup?
10
12
11
13
Strimzi makes running Apache Kafka on Kubernetes straightforward, but **backup and disaster recovery remain unsolved problems** in the Strimzi ecosystem:
12
14
13
15
-**MirrorMaker2 is not a backup** — it requires a full secondary cluster, expensive cross-cluster replication, and complex client failover procedures.
14
16
-**PVC snapshots are fragile** — deleting Strimzi CRDs triggers garbage collection of PVCs, and node failures can result in permanent data loss.
15
17
-**No point-in-time recovery** — there is no native mechanism to restore a Strimzi Kafka cluster to a specific moment in time.
16
-
-**No Strimzi-native backup CRD** — backup workflows are entirely manual or require external tools that don't integrate with the Strimzi operator model.
18
+
-**No Strimzi-compatible backup CRD** — backup workflows are entirely manual or require external tools that don't integrate with the Strimzi operator model.
17
19
18
-
The **Strimzi Backup Operator** solves these problems with a purpose-built Kubernetes operator that follows Strimzi conventions and extends the Strimzi ecosystem with first-class backup and restore capabilities.
20
+
The **Kafka Backup Operator** solves these problems with a purpose-built Kubernetes operator that follows Strimzi conventions and is designed to work with Strimzi-managed clusters, providing first-class backup and restore capabilities.
19
21
20
22
## Features
21
23
22
-
-**Strimzi-native CRDs** — `KafkaBackup` and `KafkaRestore` custom resources under the `backup.strimzi.io` API group, following Strimzi conventions for status conditions, labels, and finalizers
24
+
-**Strimzi-compatible CRDs** — `KafkaBackup` and `KafkaRestore` custom resources under the `kafkabackup.com` API group, following Strimzi conventions for status conditions, labels, and finalizers
23
25
-**Auto-discovery of Strimzi resources** — automatically resolves bootstrap servers, TLS certificates, and KafkaUser credentials from your existing Strimzi `Kafka` CRs
24
-
-**Scheduled Strimzi backups** — cron-based scheduling with timezone support via Kubernetes CronJobs
25
-
-**Point-in-time recovery (PITR)** — restore your Strimzi Kafka cluster to any millisecond-precision timestamp
26
+
-**Scheduled backups** — cron-based scheduling with timezone support via Kubernetes CronJobs
27
+
-**Point-in-time recovery (PITR)** — restore your Kafka cluster to any millisecond-precision timestamp
26
28
-**Multi-cloud storage** — back up to Amazon S3, Azure Blob Storage, Google Cloud Storage, or any S3-compatible store (MinIO, Ceph RGW)
27
29
-**Topic filtering** — include/exclude topics using regex patterns
28
30
-**Topic mapping** — rename topics during restore for migration or testing scenarios
@@ -35,14 +37,14 @@ The **Strimzi Backup Operator** solves these problems with a purpose-built Kuber
35
37
36
38
## Architecture
37
39
38
-
The Strimzi Backup Operator creates Kubernetes Jobs (or CronJobs for scheduled backups) that run the `kafka-backup` CLI to perform backup and restore operations. This provides resource isolation, failure isolation, and pod-level customisation.
40
+
The Kafka Backup Operator creates Kubernetes Jobs (or CronJobs for scheduled backups) that run the `kafka-backup` CLI to perform backup and restore operations. This provides resource isolation, failure isolation, and pod-level customisation.
| `KafkaBackup` | `kb` | `backup.strimzi.io/v1alpha1` | Defines a Strimzi backup configuration with scheduling, retention, and storage |
151
-
| `KafkaRestore` | `kr` | `backup.strimzi.io/v1alpha1` | Defines a restore operation with PITR, topic mapping, and consumer group restore |
152
+
| `KafkaBackup` | `kb` | `kafkabackup.com/v1alpha1` | Defines a backup configuration with scheduling, retention, and storage |
153
+
| `KafkaRestore` | `kr` | `kafkabackup.com/v1alpha1` | Defines a restore operation with PITR, topic mapping, and consumer group restore |
152
154
153
155
## Storage Configuration
154
156
@@ -207,7 +209,7 @@ storage:
207
209
key: credentials
208
210
```
209
211
210
-
## Strimzi Backup Authentication
212
+
## Authentication
211
213
212
214
The operator automatically discovers TLS certificates and authentication credentials from your Strimzi cluster. You can also reference `KafkaUser` CRs directly:
0 commit comments