AlloyDB Omni using the container orchestrator refers to the use of Kubernetes as an orchestrator for deploying and managing AlloyDB Omni databases. This deployment model enables automated provisioning and API-driven lifecycle management of your database deployments.
Use the container orchestrator deployment option when you need containerization and orchestration to support highly scalable and manageable database instances, particularly for modern workloads in environments like on-premises, multi-cloud, or Google Distributed Cloud.
Use cases
The AlloyDB Omni Kubernetes operator supports the following use cases:
- Automated provisioning and API-driven lifecycle management.
- Configurable high availability to fine-tune failover mechanisms.
- Sidecar support for integrating enterprise backup or monitoring agents.
- Variable read pools for scaling read-only operations.
- Load balancing with server-side connection pooling with PgBouncer.
- Platform support and marketplace availability for Google Distributed Cloud and Red Hat OpenShift.
- Cross-region disaster recovery to create standby databases in remote clusters, data centers, and regions.
You can also pair your Kubernetes deployment with the optional AlloyDB Omni web user interface, a self-managed web console that provides observability dashboards for cluster instances, system telemetry charts, database sizes, active database flags, columnar engine statistics, and query insights.
Get started
- Learn about the AlloyDB Omni availability reference architecture.
- Install the AlloyDB Omni Kubernetes operator.
- Install the web UI using the container orchestrator.