Skip to content

Databases

Root & Branch Cloud offers managed database instances that run in your project’s Kubernetes namespace. Databases are backed up automatically and support version upgrades.

Database Operator Default version Default storage
PostgreSQL CloudNativePG 18.4 10 Gi
MySQL InnoDB Cluster 8.4.9 3 Gi
Redis Opstree Redis Operator v8.6.2 1 Gi

PostgreSQL databases connect via ProxySQL at pg.rootandbranch.io. MySQL databases are registered in ProxySQL and can be reached through the same gateway. Redis databases provide a TLS-enabled external connection at rediss://.

  1. Open your project and go to the Databases tab.
  2. Click New database.
  3. Select the database type (PostgreSQL, MySQL, or Redis).
  4. Enter a name.
  5. Choose a version from the available list.
  6. Optionally adjust the resource tier and storage size.
  7. Click Create.

The platform provisions resources in the background. You can monitor the provisioning status from the database detail page.

You need the database.create permission to provision a database.

Once the database is running, connection details are shown on the database detail page:

  • Host - the ProxySQL gateway or Redis endpoint.
  • Port - the database port.
  • Username and password - auto-generated credentials.
  • Connection string - a ready-to-use URI.

Credentials are generated at provisioning time and stored as Kubernetes secrets.

Database versions can be upgraded from the database settings. Only forward version upgrades are supported - you cannot downgrade to an older version. The version catalogue defines which versions are available and supported.

Before upgrading, ensure no backup or restore operation is currently running.

Managed databases are backed up via the rab-cloud-database-backup system. You can:

  • View backups from the database detail page.
  • Create a backup on demand.
  • Restore a backup to a specific point.

You can adjust CPU, memory, and storage at any time from the database settings. The platform performs a Helm upgrade to apply the changes. The database remains available during resource changes for PostgreSQL (via CNPG rolling updates). MySQL requires a minimum of 1 vCPU and 1 Gi of memory - smaller tiers are not available for MySQL workloads.

Deleting a database removes its Helm release, all associated Kubernetes resources, and all backups. This action is permanent.

You need the database.delete permission.