AlloyDB Omni 연산자 1.0.0 이상 버전을 실행하는 경우 다음 단계는 업그레이드하려는 AlloyDB Omni 버전에 따라 달라집니다. AlloyDB Omni 버전 번호에는 다음 구성요소가 있습니다.
PostgreSQL 호환성의 주요 버전 번호
PostgreSQL 호환성의 마이너 버전 번호
이 AlloyDB Omni 출시의 패치 버전 번호
예를 들어 AlloyDB Omni 버전 16.3.0은 PostgreSQL 버전 15.7을 지원하며 AlloyDB Omni 출시 패치가 없습니다.
타겟 버전에 적합한 설치 옵션을 선택합니다.
설치 시나리오
업데이트 단계
최신 버전의 PostgreSQL을 지원하는 AlloyDB Omni 버전으로 업그레이드하려고 합니다.
AlloyDB Omni 연산자와 데이터베이스 클러스터를 업그레이드합니다.
특정 PostgreSQL 부 버전을 지원하는 각 AlloyDB Omni 출시 세트에는 자체 AlloyDB Omni 연산자 버전 번호가 있습니다. AlloyDB Omni 연산자 버전 호환성 표를 사용하여 AlloyDB Omni 연산자 버전이 연산자 버전과 호환되는지 확인합니다.
DB_CLUSTER_NAME: 데이터베이스 클러스터의 이름입니다.
데이터베이스 클러스터를 만들 때 선언한 데이터베이스 클러스터 이름과 동일합니다.
자세한 내용은 Kubernetes에 AlloyDB Omni 설치를 참고하세요.
업그레이드가 완료될 때까지 기다립니다.
업그레이드 전에 HA를 사용 중지한 경우 다음 단계를 완료하세요.
클러스터의 매니페스트에서 numberOfStandbys를 업그레이드 전의 숫자로 다시 설정합니다.
매니페스트를 다시 적용하여 HA를 다시 사용 설정합니다.
alloydb_omni_instance_postgresql_wait_time_second_total 업데이트
alloydb_omni_instance_postgresql_wait_time_second_total 측정항목을 사용하는 경우 alloydb_omni_instance_postgresql_wait_time_us_total로 업데이트해야 합니다. 두 측정항목을 모두 사용하려면 Prometheus OR 연산자를 사용하세요.
(promQL A) OR (promQL A, but replace all occurrences of alloydb_omni_instance_postgresql_wait_time_second_total to alloydb_omni_instance_postgresql_wait_time_us_total)
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-03(UTC)"],[],[],null,["# Upgrade your AlloyDB Omni Kubernetes operator to version 1.4.0\n\nSelect a documentation version: 16.3.0keyboard_arrow_down\n\n- [Current (16.8.0)](/alloydb/omni/current/docs/upgrade-kubernetes-operator-version)\n- [16.8.0](/alloydb/omni/16.8.0/docs/upgrade-kubernetes-operator-version)\n- [16.3.0](/alloydb/omni/16.3.0/docs/upgrade-kubernetes-operator-version)\n- [15.12.0](/alloydb/omni/15.12.0/docs/upgrade-kubernetes-operator-version)\n- [15.7.1](/alloydb/omni/15.7.1/docs/upgrade-kubernetes-operator-version)\n\n\u003cbr /\u003e\n\nThis page describes how to upgrade the AlloyDB Omni operator to version 1.4.0. The steps to upgrade depend on your current version of AlloyDB Omni and the version that you upgrade to.\n\n\u003cbr /\u003e\n\nBefore you begin\n----------------\n\nWhen you upgrade the AlloyDB Omni operator, the database\nrestarts unless all of the following are true:\n\n- You're upgrading the AlloyDB Omni operator version 1.1.1 to a newer version.\n- You're using the AlloyDB Omni database version 15.5.5 or later.\n- AlloyDB AI is not enabled. For more information, see [Create a database cluster with AlloyDB AI](/alloydb/omni/16.3.0/docs/install-with-alloydb-ai?resource=kubernetes#enable-alloydb-ai).\n\nIf the database restarts, no data loss is expected.\n\nStarting from the AlloyDB Omni database version 15.7.1, high\navailability (HA) on your Kubernetes-based AlloyDB Omni database\nclusters uses a new architecture to provide more hardening and improvements for\nHA automatic setup, failover, and healing capabilities.\n\nIf you're upgrading the AlloyDB Omni database version from\n15.7.0 (or earlier) to version 15.7.1 (or later), or if you're downgrading\nversions, you must disable HA, and you must re-enable HA after the process\ncompletes.\n\nDetermine your current versions\n-------------------------------\n\nTo check the version of AlloyDB Omni used by your database\ncluster, run the following command: \n\n kubectl get dbclusters.alloydbomni.dbadmin.goog \u003cvar translate=\"no\"\u003eDB_CLUSTER_NAME\u003c/var\u003e -n \u003cvar translate=\"no\"\u003eNAMESPACE\u003c/var\u003e -o jsonpath='{.status.primary.currentDatabaseVersion}'\n\nMake the following replacements:\n\n- \u003cvar translate=\"no\"\u003eDB_CLUSTER_NAME\u003c/var\u003e: the name of your database cluster. It's\n the same database cluster name that you declared when you created it. For\n more information, see\n [Install AlloyDB Omni on Kubernetes](/alloydb/omni/16.3.0/docs/deploy-kubernetes#create).\n\n- \u003cvar translate=\"no\"\u003eNAMESPACE\u003c/var\u003e: the Kubernetes namespace of your database\n cluster.\n\nIf you run version 1.0.0 or later of the AlloyDB Omni operator, then this\ncommand prints the version of AlloyDB Omni used by your database\ncluster.\n\nTo check the version of the AlloyDB Omni operator installed on your\nKubernetes cluster, run the following command: \n\n kubectl get dbclusters.alloydbomni.dbadmin.goog \u003cvar translate=\"no\"\u003eDB_CLUSTER_NAME\u003c/var\u003e -n \u003cvar translate=\"no\"\u003eNAMESPACE\u003c/var\u003e -o jsonpath='{.status.primary.currentControlPlaneAgentsVersion}'\n\nIf you run version 1.0.0 or later of the AlloyDB Omni operator, the\noutput is the version number of the AlloyDB Omni operator running on your\nKubernetes cluster.\n\nIf you run a version of AlloyDB Omni operator earlier than\n1.0.0, follow the instructions in\n[Upgrade from a pre-1.0.0 AlloyDB Omni operator](/alloydb/omni/16.3.0/docs/manage#older-operator).\nOtherwise,\n[check your target version numbers](#check-target-version).\n\nCheck your target version numbers\n---------------------------------\n\nIf you run a version of AlloyDB Omni operator 1.0.0 or later, then\nyour next steps depend on the version of AlloyDB Omni that\nyou want to upgrade to. The AlloyDB Omni version number has\nthe following components:\n\n- The major version number of its PostgreSQL compatibility\n- The minor version number of its PostgreSQL compatibility\n- The patch version number of this AlloyDB Omni release\n\nFor example, AlloyDB Omni version 16.3.0\nsupports PostgreSQL version 15.7 and doesn't have a AlloyDB Omni\nrelease patch.\n\nChoose the installation option that works for your target version:\n\nUpgrade the AlloyDB Omni operator\n---------------------------------\n\nTo upgrade the AlloyDB Omni operator, follow these steps:\n\n1. Define the environment variables:\n\n export GCS_BUCKET=alloydb-omni-operator\n export OPERATOR_VERSION=\u003cvar translate=\"no\"\u003eOPERATOR_VERSION\u003c/var\u003e\n export HELM_PATH=$OPERATOR_VERSION/alloydbomni-operator-$OPERATOR_VERSION.tgz\n\n Replace \u003cvar translate=\"no\"\u003eOPERATOR_VERSION\u003c/var\u003e with the version of the\n AlloyDB Omni operator that you're upgrading to---for example,\n `1.4.0`.\n2. Download the latest AlloyDB Omni operator:\n\n gcloud storage cp -r gs://$GCS_BUCKET/$HELM_PATH ./\n tar -xvzf alloydbomni-operator-${OPERATOR_VERSION}.tgz\n\n3. Apply the latest AlloyDB Omni operator custom resource definitions:\n\n kubectl apply -f alloydbomni-operator/crds\n\n4. Upgrade the AlloyDB Omni operator Helm chart:\n\n helm upgrade alloydbomni-operator alloydbomni-operator-${OPERATOR_VERSION}.tgz \\\n --namespace alloydb-omni-system \\\n --atomic \\\n --timeout 5m\n\nUpdate the database clusters\n----------------------------\n\nTo update the `dbCluster`, complete the following steps:\n\n1. If you're upgrading an HA AlloyDB Omni database cluster from\n database version 15.7.0 (or earlier) to version 15.7.1 (or later), follow\n these steps to disable HA.\n\n | **Note:** If you're upgrading from an older version to version 15.7.0 (or earlier), or from version 15.7.1 (or later) to a newer version, skip this step.\n 1. Set the `numberOfStandbys` to `0` in the cluster's manifest.\n\n spec:\n availability:\n numberOfStandbys: 0\n\n 1. To disable HA, re-apply the manifest.\n2. Update the `databaseVersion` and the `controlPlaneAgentsVersion` versions in\n the cluster's manifest, and re-apply the manifest.\n\n Run the following example, which is part of a manifest file that specifies version\n 16.3.0 of `databaseVersion` and version\n 1.4.0 of `controlPlaneAgentsVersion`: \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: \"16.3.0\"\n controlPlaneAgentsVersion: \"1.4.0\"\n ...\n\n Replace the following variable:\n - \u003cvar translate=\"no\"\u003eDB_CLUSTER_NAME\u003c/var\u003e: the name of your database cluster. It's the same database cluster name that you declared when you created it. For more information, see [Install AlloyDB Omni on Kubernetes](/alloydb/omni/16.3.0/docs/deploy-kubernetes#create).\n3. Wait for the upgrade to complete successfully.\n\n4. If you disabled HA before the upgrade, complete the following steps.\n\n 1. Set the `numberOfStandbys` back to the number prior to upgrade in the\n cluster's manifest.\n\n 2. Re-apply the manifest to re-enable HA.\n\nUpdate `alloydb_omni_instance_postgresql_wait_time_second_total`\n----------------------------------------------------------------\n\nIf you're using the `alloydb_omni_instance_postgresql_wait_time_second_total`\nmetric, you must update it to\n`alloydb_omni_instance_postgresql_wait_time_us_total`. To consume both metrics,\nuse the Prometheus `OR` operator. \n\n (promQL A) OR (promQL A, but replace all occurrences of alloydb_omni_instance_postgresql_wait_time_second_total to alloydb_omni_instance_postgresql_wait_time_us_total)\n\nIf you use `seconds` as the unit for this metric, you must convert it\nto `us`.\n\nFor more information, see the [release notes](/alloydb/omni/16.3.0/docs/release-notes)."]]
