Configure AlloyDB Omni

This page shows how to configure AlloyDB Omni after you have installed it.

Single-server

Change your data directory location

AlloyDB Omni has a default configuration file named dataplane.conf that's present in the /var/alloydb/config directory. To change your server's data directory location, update the DATADIR_PATH variable in the dataplane.conf file.

To update the DATADIR_PATH variable in dataplane.conf, run the following command:

sudo sed -i "s|^\(DATADIR_PATH=\).*|\1DATA_DIRECTORY|" /var/alloydb/config/dataplane.conf

Replace DATA_DIRECTORY with the full file system path to the existing directory that you want to contain your AlloyDB Omni installation.

Alternately, use a text editor to open dataplane.conf and update the value of the DATADIR_PATH directive.

Note: Set the value of DATADIR_PATH to the directory that contains the data subdirectory—for example, $HOME/alloydb and not $HOME/alloydb/data.

Configure other server options

The /var/alloydb/config directory also contains the following two standard PostgreSQL configuration files:

• postgresql.conf
• pg_hba.conf

The AlloyDB Omni installer populates both of these files with default values to get you started. You can update both files in whatever way is appropriate for your own needs.

Caution: AlloyDB Omni copies these files into your data directory for its own runtime use. Edit only the files in /var/alloydb/config, and not the copies in your data directory. Otherwise, any changes you make to those files risk being overwritten.

Kubernetes

You configure and control a Kubernetes-based AlloyDB Omni database cluster by pairing declarative manifest files with the kubectl utility, just like any other Kubernetes-based deployment.

Some resources that you can configure are:

• Manage backup and restore
• Create read pool instance in Kubernetes
• Use a sidecar container in Kubernetes

What's next

• Run and connect to AlloyDB Omni

• Manage AlloyDB Omni

• Create a read-only replica