YugabyteDB

The following table describes the operating system and architecture support for deploying YugabyteDB.

Unless otherwise noted, operating systems are supported by all supported versions of YugabyteDB and YugabyteDB Anywhere. YugabyteDB Anywhere added support for deploying YugabyteDB to ARM-based systems for non-Kubernetes platforms in v2.18.

Operating system x86 ARM Notes
AlmaLinux 8 Recommended for production
Recommended development platform
Default for YugabyteDB Anywhere-deployed nodes
AlmaLinux 9
Oracle Linux 8
Red Hat Enterprise Linux 8 Recommended for production
Red Hat Enterprise Linux 8 CIS Hardened
Red Hat Enterprise Linux 9.3 and later Supported in v2.20.3 and later. EA
Red Hat Enterprise Linux 9 CIS Hardened Supported in v2.20.3 and later. EA
SUSE Linux Enterprise Server 15 SP5 EA
Ubuntu 20
Ubuntu 22 Supported in v2.18.5, v2.20.1

The following table describes operating systems and architectures that are no longer supported for deploying YugabyteDB.

Operating system x86 ARM Notes
Amazon Linux 2 Supported in v2.18.0 and later
Deprecated in v2.20
Removed support in v2.21.
CentOS 7 Deprecated in v2.20
Removed support in v2.21.
Oracle Linux 7 Deprecated in v2.20
Removed support in v2.21.
Red Hat Enterprise Linux 7 Deprecated in v2.20
Removed support in v2.21.
Ubuntu 18 Deprecated in v2.20
Removed support in v2.21.

Using CIS hardened operating systems

YugabyteDB supports RHEL CIS hardened operating systems based on the following images:

To use these images for YugabyteDB or YugabyteDB Anywhere, you need to make the following modifications.

YugabyteDB clusters

To use a CIS hardened image for cluster nodes:

  1. Install the image on the nodes.
  2. Change the firewall rules.

YugabyteDB Anywhere

To use a CIS hardened image for installing YugabyteDB Anywhere:

  1. Install the image on the node.
  2. Change the firewall rules for YugabyteDB Anywhere installation.

YugabyteDB Anywhere universe

To use a CIS hardened image for on-premises universe nodes:

  1. Install the image on the nodes.
  2. Change the firewall rules.
  3. If you want SSH access to database nodes, during provisioning, add the yugabyte user to sshd_config.
  4. Create a custom tmp directory during provisioning.
  5. After you create the on-premises provider, set the provider runtime configuration flag yb.filepaths.remoteTmpDirectory to the custom tmp directory.
  6. When creating universes using the provider, set YB-Master and YB-TServer configuration flag tmp_dir to the custom tmp directory.

To use a CIS hardened image for universes on cloud providers:

  1. Download the image.
  2. Change the firewall rules.
  3. Upload the modified image to your cloud provider.
  4. Add the modified image to the Linux version catalog.