Platform backup and restore

Platform backups cover the platform's own state: the secrets in OpenBao, and the cluster's TLS certificates with the issuer accounts that requested them. Both go to object storage every 10 minutes and are restored automatically when a cluster is rebuilt. Cluster configuration does not need a backup because it lives in Git, and Argo CD applies it again to a new cluster.

Secrets backup and restore

Project: GlueOps backup-tools, vault-backup-validator and vault-init-controller (GlueOps open source) · License: Apache License 2.0

OpenBao is backed up to object storage every 10 minutes. A validation service checks that a backup can be restored and contains the expected secrets. When a cluster is built again, OpenBao is restored from backup during bootstrap.

OpenBao secrets and cert-manager certificates are backed up to object storage every 10 minutes and restored when a cluster is built again; Argo CD applies the platform configuration from Git. Applications redeploy from their deployment repositories; application data is not part of platform backups.

Project docs Source code

Certificate backup and restore

Project: GlueOps certs-backup-restore (GlueOps open source) · License: Apache License 2.0

The cluster's TLS certificates are backed up to object storage every 10 minutes, together with the cert-manager issuers and the account keys they use with the certificate authority. When a cluster is built again, they are restored during bootstrap.

Project docs Source code

GlueOps's own code is released under the Apache License 2.0. Each upstream project keeps its own license, shown in its section. Project names and logos belong to their owners and are shown only to identify each project. Their use does not mean that any project endorses GlueOps.

More of the platform

Questions about the platform?

Talk to an engineer.

Book a free assessment and we'll walk through how the platform would run your workloads.

Get a free assessment