Skip to main content
Version: 3.2

KVDB for Portworx in OCP on bare metal

Summary and Key concepts

Summary:​

This article explains the role of the Key-Value Database (KVDB) in Portworx, which stores the cluster's state, configuration, and metadata for storage volumes and snapshots. While Portworx recommends using the built-in internal KVDB for most setups, there are specific scenarios where an external KVDB is required, such as when configuring synchronous disaster recovery (DR) or when the Portworx cluster includes both Kubernetes and non-Kubernetes nodes. The article then directs users to further resources depending on their choice of KVDB and installation method.

Kubernetes Concepts:​

  • Kubernetes Nodes: Kubernetes nodes can be part of a Portworx cluster and participate in KVDB configurations.

Portworx Concepts:​

  • Synchronous DR: A setup that requires external KVDB for high availability across different clusters.

Portworx uses a key-value database (KVDB) to store the cluster's state, configuration data, and metadata associated with storage volumes and snapshots.

note

Portworx recommends using the built-in internal KVDB for your Portworx cluster. However, you will need to use an external KVDB in the following scenarios:

  • When configuring a synchronous DR setup.
  • When your Portworx cluster spans a combination of Kubernetes and non-Kubernetes nodes.

Proceed to one of the topics depending on how you are planning to install Portworx and whether you choose internal or external KVDB.

Last updated on
Was this page helpful?