Backends

Kuma supports a few different backends that we can use when running kuma-cp. You can configure the backend storage by setting the environment variable when running the control plane.

This information has been documented for clarity, but when following the installation instructions these settings will be automatically configured.

Kuma stores all the state in-memory. This means that restarting Kuma will delete all the data. Only recommend when playing with Kuma locally. For example:

This is the default memory store if KUMA_STORE_TYPE is not being specified.

Kuma stores all the state in a PostgreSQL database. Used when running in Universal mode. You can also use a remote PostgreSQL database offered by any cloud vendor. For example:

To provide easy upgrades between Kuma versions there is a migration system of Postgres DB schema.

Kuma CP at start will check if the current DB schema is compatible with the version of Kuma you are trying to run. Information about current newest migration is stored in schema_migration table.