Overview
A SchemaRegistryBackup is used for backing up schemas from a SchemaRegistry, and offloading them to a Storage. It is configured by creating a SchemaRegistryBackup resource in Kubernetes.
The Kannika Armory Operator creates a Pod that runs the backup process, based on the configuration in the SchemaRegistryBackup resource.
Usage
SchemaRegistryBackups can be managed using the kubectl
command line tool,
and are available by the name schemaregistrybackup
or schemaregistrybackups
.
Backup Status
A SchemaRegistryBackup can have the following statuses:
- Initializing The backup process is being created
- Running The backup process is running
- Error The backup process has encountered an error
Configuring a SchemaRegistryBackup
The following is an example of a SchemaRegistryBackup.
In this example:
-
A SchemaRegistryBackup named
confluent-registry-backup
is created, as indicated by the.metadata.name
field. This name will inherited by the Pod running the backup process. -
The SchemaRegistryBackup will connect to the
confluent-registry
SchemaRegistry to fetch schemas, as indicated by the.spec.registry
field, and use the Credentials referenced byconfluent-registry-creds
for authentication. -
The SchemaRegistryBackup will write data to the
local-storage
Storage defined in thespec.storage
field. -
The interval between API fetches and synchronization with the remote storage is set to 15 seconds by the
spec.backupIntervalSecs
field. If not specified, backups will occur every 3600 seconds.