Halaman ini memberikan ringkasan Operator Kubernetes AlloyDB Omni, dengan petunjuk
untuk menggunakannya guna men-deploy AlloyDB Omni ke cluster Kubernetes. Halaman
ini mengasumsikan Anda telah memiliki pengetahuan dasar tentang operasi Kubernetes.
Untuk mengetahui petunjuk cara menginstal AlloyDB Omni ke lingkungan Linux standar, lihat Menginstal AlloyDB Omni.
Ringkasan
Untuk men-deploy AlloyDB Omni ke cluster Kubernetes, instal
Operator AlloyDB Omni, ekstensi ke Kubernetes API yang disediakan oleh
Google.
Anda mengonfigurasi dan mengontrol cluster database AlloyDB Omni berbasis Kubernetes dengan menyandingkan file manifes deklaratif dengan utilitas kubectl, seperti deployment berbasis Kubernetes lainnya. Anda tidak menggunakan CLI
AlloyDB Omni, yang ditujukan untuk
deployment ke masing-masing mesin Linux, bukan cluster Kubernetes.
Sebelum memulai
Anda memerlukan akses ke hal berikut:
Cluster Kubernetes, yang menjalankan software berikut:
Jika Anda perlu menginstal gcloud CLI, perhatikan bahwa langkah-langkah
menjalankan gcloud init bersifat opsional. Menginstal AlloyDB Omni
tidak memerlukan autentikasi dengan Akun Google.
Setiap node di cluster Kubernetes harus memiliki hal berikut:
Minimal dua CPU x86 atau AMD64.
Minimum RAM 8 GB.
Kernel Linux versi 4.18 atau yang lebih baru.
Grup kontrol v2 (cgroup v2) diaktifkan.
Menginstal Operator AlloyDB Omni
Untuk menginstal Operator AlloyDB Omni, ikuti langkah-langkah berikut:
Penginstalan yang berhasil akan menampilkan output berikut:
NAME: alloydbomni-operator
LAST DEPLOYED: CURRENT_TIMESTAMP
NAMESPACE: alloydb-omni-system
STATUS: deployed
REVISION: 1
TEST SUITE: None
Lakukan pembersihan dengan menghapus file penginstalan AlloyDB Omni Operator yang didownload. File ini diberi nama
alloydbomni-operator-VERSION_NUMBER.tgz, dan berada di
direktori kerja Anda saat ini.
Membuat cluster database
Cluster database AlloyDB Omni berisi semua penyimpanan dan
resource komputasi yang diperlukan untuk menjalankan server AlloyDB Omni, termasuk
server utama, replika, dan semua data Anda.
Setelah menginstal Operator AlloyDB Omni di cluster Kubernetes, Anda dapat membuat cluster database AlloyDB Omni di cluster Kubernetes dengan menerapkan manifes yang mirip dengan berikut ini:
DB_CLUSTER_NAME: nama cluster database ini—misalnya, my-db-cluster.
ENCODED_PASSWORD: sandi login database untuk peran pengguna postgres default, yang dienkode sebagai string base64—misalnya, Q2hhbmdlTWUxMjM= untuk ChangeMe123.
CPU_COUNT: jumlah CPU yang tersedia untuk setiap instance database dalam cluster database ini.
MEMORY_SIZE: jumlah memori per instance database dari cluster database ini. Sebaiknya tetapkan setelan ini ke 8 gigabyte per CPU. Misalnya, jika Anda menetapkan cpu ke 2 sebelumnya dalam manifes ini, sebaiknya tetapkan memory ke 16Gi.
DISK_SIZE: ukuran disk per instance database—misalnya, 10Gi.
Setelah Anda menerapkan manifes ini, cluster Kubernetes Anda akan berisi cluster database AlloyDB Omni dengan konfigurasi memori, CPU, dan penyimpanan yang ditentukan. Untuk membuat koneksi pengujian dengan cluster database baru, lihat Menghubungkan menggunakan psql yang sudah diinstal sebelumnya.
Untuk mengetahui informasi selengkapnya tentang manifes Kubernetes dan cara menerapkannya, lihat
Mengelola
resource.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-03 UTC."],[[["\u003cp\u003eThis guide outlines how to deploy AlloyDB Omni onto a Kubernetes cluster using the AlloyDB Omni Operator, which is an extension to the Kubernetes API.\u003c/p\u003e\n"],["\u003cp\u003eDeployment on Kubernetes requires the AlloyDB Omni Operator and the \u003ccode\u003ekubectl\u003c/code\u003e utility, and does not use the AlloyDB Omni CLI intended for Linux machines.\u003c/p\u003e\n"],["\u003cp\u003eBefore beginning, you need a Kubernetes cluster running version 1.21 or later, the \u003ccode\u003ecert-manager\u003c/code\u003e service, \u003ccode\u003ekubectl\u003c/code\u003e, \u003ccode\u003ehelm\u003c/code\u003e, and the Google Cloud CLI.\u003c/p\u003e\n"],["\u003cp\u003eTo install the AlloyDB Omni Operator, set environment variables, download the operator, and use the \u003ccode\u003ehelm install\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eCreating a database cluster involves applying a manifest file that specifies the cluster name, database version, resources, and encoded password, among other configurations.\u003c/p\u003e\n"]]],[],null,["# Install AlloyDB Omni on Kubernetes\n\nSelect a documentation version: 15.5.4keyboard_arrow_down\n\n- [Current (16.8.0)](/alloydb/omni/current/docs/deploy-kubernetes)\n- [16.8.0](/alloydb/omni/16.8.0/docs/deploy-kubernetes)\n- [16.3.0](/alloydb/omni/16.3.0/docs/deploy-kubernetes)\n- [15.12.0](/alloydb/omni/15.12.0/docs/deploy-kubernetes)\n- [15.7.1](/alloydb/omni/15.7.1/docs/deploy-kubernetes)\n- [15.7.0](/alloydb/omni/15.7.0/docs/deploy-kubernetes)\n- [15.5.5](/alloydb/omni/15.5.5/docs/deploy-kubernetes)\n- [15.5.4](/alloydb/omni/15.5.4/docs/deploy-kubernetes)\n- [15.5.2](/alloydb/omni/15.5.2/docs/deploy-kubernetes)\n\n\u003cbr /\u003e\n\n| **Note:** Your use of AlloyDB Omni is subject to the agreement between you and Google that governs Google Cloud offerings. If you do not have a Google Cloud account, or have not otherwise entered into an agreement with Google that governs Google Cloud offerings, please do not proceed or download this software until you have done so. To create a Google Cloud account, see [the Google Cloud homepage](/docs/get-started).\n\n\u003cbr /\u003e\n\nThis page provides an overview of the AlloyDB Omni Kubernetes Operator, with instructions\nfor using it to deploy AlloyDB Omni onto a Kubernetes cluster. This\npage assumes basic familiarity with Kubernetes operation.\n\nFor instructions on installing AlloyDB Omni onto a standard Linux\nenvironment, see [Install AlloyDB Omni](/alloydb/omni/15.5.4/docs/install).\n\nOverview\n--------\n\nTo deploy AlloyDB Omni onto a Kubernetes cluster, install the\nAlloyDB Omni Operator, an extension to the Kubernetes API provided by\nGoogle.\n\nYou configure and control a Kubernetes-based AlloyDB Omni database\ncluster by pairing declarative manifest files with the `kubectl` utility, just\nlike any other Kubernetes-based deployment. You do not use [the\nAlloyDB Omni CLI](/alloydb/docs/omni/15.5.2/omni-cli), which is intended for\ndeployments onto individual Linux machines and not Kubernetes clusters.\n\nBefore you begin\n----------------\n\nYou need access to the following:\n\n- A Kubernetes cluster, running the following software:\n - Kubernetes version 1.21 or later.\n - [The `cert-manager` service](https://cert-manager.io/docs/installation).\n- [The `kubectl` utility](https://kubernetes.io/docs/tasks/tools/#kubectl).\n- [The `helm` package manager](https://helm.sh/docs/intro/install/).\n- The [Google Cloud CLI](/sdk/docs/install).\n\n If you do need to install the gcloud CLI, note that the step of\n running `gcloud init` is optional. Installing AlloyDB Omni\n does not require authentication with a Google Account.\n\nEach node in the Kubernetes cluster must have the following:\n\n- A minimum of two x86 or AMD64 CPUs.\n- At least 8GB of RAM.\n- Linux kernel version 4.18 or later.\n- Control group v2 (cgroup v2) enabled.\n\nInstall the AlloyDB Omni Operator\n---------------------------------\n\nTo install the AlloyDB Omni Operator, follow these steps:\n\n1. Define several environment variables:\n\n export GCS_BUCKET=alloydb-omni-operator\n export HELM_PATH=$(gcloud storage cat gs://$GCS_BUCKET/latest)\n export OPERATOR_VERSION=\"${HELM_PATH%%/*}\"\n\n2. Download the AlloyDB Omni Operator:\n\n gcloud storage cp -r gs://$GCS_BUCKET/$HELM_PATH ./\n\n3. Install the AlloyDB Omni Operator:\n\n helm install alloydbomni-operator alloydbomni-operator-${OPERATOR_VERSION}.tgz \\\n --create-namespace \\\n --namespace alloydb-omni-system \\\n --atomic \\\n --timeout 5m\n\n Successful installation displays the following output: \n\n NAME: alloydbomni-operator\n LAST DEPLOYED: \u003cvar translate=\"no\"\u003eCURRENT_TIMESTAMP\u003c/var\u003e\n NAMESPACE: alloydb-omni-system\n STATUS: deployed\n REVISION: 1\n TEST SUITE: None\n\n4. Clean up by deleting the downloaded AlloyDB Omni Operator\n installation file. The file is named\n `alloydbomni-operator-`\u003cvar translate=\"no\"\u003eVERSION_NUMBER\u003c/var\u003e`.tgz`, and is located in\n your current working directory.\n\nCreate a database cluster\n-------------------------\n\nAn AlloyDB Omni *database cluster* contains all the storage and\ncompute resources needed to run an AlloyDB Omni server, including\nthe primary server, any replicas, and all of your data.\n\nAfter you install the AlloyDB Omni Operator on your Kubernetes cluster,\nyou can create an AlloyDB Omni database cluster on the Kubernetes\ncluster by applying a manifest similar to the following: \n\n apiVersion: v1\n kind: Secret\n metadata:\n name: db-pw-\u003cvar translate=\"no\"\u003eDB_CLUSTER_NAME\u003c/var\u003e\n type: Opaque\n data:\n \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-nt\"\u003eDB_CLUSTER_NAME\u003c/span\u003e\u003c/var\u003e: \"\u003cvar translate=\"no\"\u003eENCODED_PASSWORD\u003c/var\u003e\"\n ---\n apiVersion: alloydbomni.dbadmin.goog/v1\n kind: DBCluster\n metadata:\n name: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eDB_CLUSTER_NAME\u003c/span\u003e\u003c/var\u003e\n spec:\n databaseVersion: \"15.5.4\"\n primarySpec:\n adminUser:\n passwordRef:\n name: db-pw-\u003cvar translate=\"no\"\u003eDB_CLUSTER_NAME\u003c/var\u003e\n resources:\n cpu: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eCPU_COUNT\u003c/span\u003e\u003c/var\u003e\n memory: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eMEMORY_SIZE\u003c/span\u003e\u003c/var\u003e\n disks:\n - name: DataDisk\n size: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eDISK_SIZE\u003c/span\u003e\u003c/var\u003e\n storageClass: standard\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eDB_CLUSTER_NAME\u003c/var\u003e: the name of this database cluster---for\n example, `my-db-cluster`.\n\n- \u003cvar translate=\"no\"\u003eENCODED_PASSWORD\u003c/var\u003e: the database login password for the\n default `postgres` user role, encoded as a base64 string---for example,\n `Q2hhbmdlTWUxMjM=` for `ChangeMe123`.\n\n- \u003cvar translate=\"no\"\u003eCPU_COUNT\u003c/var\u003e: the number of CPUs available to each\n database instance in this database cluster.\n\n- \u003cvar translate=\"no\"\u003eMEMORY_SIZE\u003c/var\u003e: the amount of memory per database instance of this\n database cluster. We recommend setting this to 8 gigabytes per CPU. For\n example, if you set `cpu` to `2` earlier in this manifest, then we recommend\n setting `memory` to `16Gi`.\n\n- \u003cvar translate=\"no\"\u003eDISK_SIZE\u003c/var\u003e: the disk size per database instance---for example, `10Gi`.\n\nAfter you apply this manifest, your Kubernetes cluster contains an\nAlloyDB Omni database cluster with the specified memory, CPU,\nand storage configuration. To establish a test connection with the new\ndatabase cluster, see [Connect using the preinstalled `psql`](/alloydb/omni/15.5.4/docs/run-connect#psql-kubernetes).\n\nFor more information about Kubernetes manifests and how to apply them, see\n[Managing\nresources](https://kubernetes.io/docs/concepts/cluster-administration/manage-deployment/).\n\nWhat's next\n-----------\n\n- [Run and connect to AlloyDB Omni](/alloydb/omni/15.5.4/docs/run-connect)\n- [Manage AlloyDB Omni](/alloydb/omni/15.5.4/docs/manage)\n- [Manage high availability in Kubernetes](/alloydb/omni/15.5.4/docs/kubernetes-ha)"]]
