---
title: Charmhub | Deploy Infra Backup Operator using Charmhub - The Open Operator
  Collection
description: Deploy the latest version of Infra Backup Operator on any cloud. Client
  charm to set backup configuration of non-workload related resources by configuring
  the velero-operator.
url: https://charmhub.io/infra-backup-operator
---

# Infra Backup Operator

[Canonical Kubernetes](https://charmhub.io/publisher/containers "View all packages from Canonical Kubernetes")

* [Canonical Kubernetes](https://charmhub.io/publisher/containers "View all packages from Canonical Kubernetes")

Platform:

24.04

edge 11

```
juju deploy infra-backup-operator --channel edge
```

[Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications)

---

#### Relevant links

* [Homepage](https://github.com/canonical/infra-backup-operator)

---

#### Contacts

* [Submit a bug](https://github.com/canonical/infra-backup-operator/issues)

---

Share your thoughts on this charm with the community on discourse.

[Join the discussion](https://discourse.charmhub.io/)

# Infra Backup Operator

The Infra Backup Operator is a Juju charm designed to work seamlessly with the [Velero Operator](https://charmhub.io/velero-operator). When related, it automatically applies the necessary configuration to enable backups of Kubernetes resources that are not tied to workloads, but to the cluster’s own configuration and infrastructure. This ensures that critical namespaces, system components, and cluster-level settings are preserved, providing a reliable safeguard for restoring the operational foundation of your Kubernetes environment.

The infra backup operator is designed to work with **any kind** of Kubernetes cluster and the backup are separated into two groups:

* Cluster Infra Backup
* Namespaced infra backup

## [Cluster Infra Backup](https://charmhub.io/infra-backup-operator#p-38580-cluster-infra-backup)

* All cluster-scoped resources (e.g., CRDs, CSRs, ClusterRoles, StorageClasses, Namespaces)
* By default, all namespaced resources in the following namespaces:
  + kube-system
  + kube-public
  + metallb-system

This behavior is controlled by the charm’s namespaces configuration option, allowing you to customize which namespaces are included in the backup process.

**Note**: While Persistent Volumes (PVs) are cluster-scoped resources, they are not included in the backup, as they are tied to workloads and should be backed up by the applications themselves. Likewise, Pods are excluded because they are ephemeral by nature and should be managed through higher-level controllers such as Deployments, StatefulSets, or DaemonSets.

## [Namespaced infra backup](https://charmhub.io/infra-backup-operator#p-38580-namespaced-infra-backup)

This will be responsible for backup the following kubernetes resources from **all namespaces**:

* Security and Access Control
  + Role, RoleBinding
  + NetworkPolicy
  + CiliumNetworkPolicies
  + ResourceQuota
  + LimitRange
  + ServiceAccount
  + Gateway and Routes (HttpRoute, TCPRoute, GRPCRoute, TLSRoute)
  + Ingress
* Configuration and Environment
  + ConfigMap
  + Secret
  + HPA / VPA
  + Jobs / CronJobs

---

[Help improve this document in the forum](https://discourse.charmhub.io/t/infra-backup-operator-documentation/18392) ([guidelines](https://discourse.charmhub.io/t/how-to-write-docs-our-documentation-guidelines-for-contributors/1245)). Last updated 1 year, 2 months ago.