이 페이지에서는 Kubernetes에서 AlloyDB Omni의 데이터베이스 부 버전을 업그레이드하는 방법을 설명합니다.
데이터베이스 부 버전 업그레이드를 수행하는 방법에는 두 가지가 있습니다.
다운타임이 적은 업그레이드: AlloyDB Omni 버전 15.7.1 이상을 실행하는 고가용성 (HA) 환경의 경우 AlloyDB Omni에서 먼저 대기 인스턴스를 업그레이드합니다. 그러면 AlloyDB Omni 연산자가 전환을 실행하여 업그레이드된 대기 인스턴스 중 하나를 새 기본 인스턴스로 승격합니다. 전환이 완료되면 이전 기본 인스턴스가 업데이트됩니다.
이 프로세스를 통해 업그레이드 중에 다운타임을 최소화할 수 있습니다.
동시 업그레이드: 그 밖의 모든 경우 AlloyDB Omni 연산자는 모든 인스턴스를 동시에 업그레이드합니다. 즉, 업그레이드 중에 다운타임이 발생합니다.
제한사항
다운타임이 적은 업그레이드의 경우 언제든지 하나의 대기 인스턴스를 사용할 수 없습니다. 데이터베이스 클러스터가 복구 시점 목표 (RPO)에 도달하지 않고 데이터 손실 위험이 없도록 하려면 데이터베이스 클러스터에 기본 인스턴스 1개와 대기 인스턴스가 2개 이상 있어야 합니다.
시작하기 전에
클러스터가 HA이고 AlloyDB Omni 버전이 15.7.1 이전인 경우 이 부 버전 업그레이드 프로세스를 따르기 전에 데이터베이스 클러스터 업데이트에 나열된 단계를 따르세요.
[[["이해하기 쉬움","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-05(UTC)"],[],[],null,["# Perform a minor database version upgrade for AlloyDB Omni on Kubernetes\n\nSelect a documentation version: 16.8.0keyboard_arrow_down\n\n- [Current (16.8.0)](/alloydb/omni/current/docs/upgrade-kubernetes-database-minor-version)\n- [16.8.0](/alloydb/omni/16.8.0/docs/upgrade-kubernetes-database-minor-version)\n- [15.12.0](/alloydb/omni/15.12.0/docs/upgrade-kubernetes-database-minor-version)\n\n\u003cbr /\u003e\n\n|\n| **Preview\n| --- [AlloyDB Omni](/alloydb/omni/16.8.0/docs/overview)**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| You can process personal data for this feature as outlined in the\n| [Cloud Data Processing\n| Addendum](/terms/data-processing-addendum), subject to the obligations and restrictions described in the agreement under\n| which you access Google Cloud.\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nThis page describes how to perform a minor database version upgrade for\nAlloyDB Omni on Kubernetes.\n\nTo perform a minor database version upgrade, there are two options:\n\n- Low downtime upgrade: For\n [high availability (HA)](/alloydb/omni/16.8.0/docs/high-availability/overview)\n environments running AlloyDB Omni version 15.7.1 or later,\n AlloyDB Omni upgrades your standby instances first. Then, the\n AlloyDB Omni operator performs a switchover, promoting one of the\n upgraded standby instances to be your new primary instance. After the\n switchover succeeds, your old primary instance is updated.\n\n This process ensures minimal downtime during the upgrade.\n- Simultaneous upgrade: For all other circumstances, the\n AlloyDB Omni operator upgrades all instances simultaneously. This\n means you will experience downtime during the upgrade.\n\nLimitations\n-----------\n\nFor low downtime upgrades, one standby instance is unavailable at any given\ntime. To ensure that your database cluster doesn't reach zero Recovery Point\nObjective (RPO) and doesn't risk losing data, your database cluster must have\none primary instance and at least two standby instances.\n\nBefore your begin\n-----------------\n\n- If your cluster is HA and the AlloyDB Omni version is older than 15.7.1, follow the steps listed in [Update the database clusters](/alloydb/omni/16.8.0/docs/upgrade-kubernetes-operator-version#update-clusters) before following this minor version upgrade process.\n- Identify a low traffic period where you can perform the minor version upgrade.\n- To avoid any data loss, [back up your data](/alloydb/omni/16.8.0/docs/backup-kubernetes).\n\nEnable the low downtime minor database version upgrade process\n--------------------------------------------------------------\n\nTo enable the low downtime minor database version upgrade process, add the\nfollowing annotation to your database cluster. \n\n```\nkubectl annotate dbclusters.alloydbomni.dbadmin.goog DB_CLUSTER_NAME\ndbcluster.dbadmin.goog/enableLDTM=true\n```\n\nReplace the following variable:\n\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 provided when you created it. For more information, see [Install AlloyDB Omni on Kubernetes](/alloydb/omni/16.8.0/docs/deploy-kubernetes#create).\n\nUpgrade your AlloyDB Omni version\n---------------------------------\n\nTo upgrade your 16.8.0 version, update the\n`databaseVersion` and the `controlPlaneAgentsVersion` fields in the cluster's\nmanifest file, and then re-apply the file.\n\nThe following is the beginning of a manifest file that specifies version\n16.8.0 for `databaseVersion` and version\n1.5.0 for `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.8.0\"\n controlPlaneAgentsVersion: \"1.5.0\"\n ...\n\nReplace the following variable:\n\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 provided when you created it. For more information, see [Install AlloyDB Omni on Kubernetes](/alloydb/omni/16.8.0/docs/deploy-kubernetes#create).\n\n### Monitor the upgrade process\n\nAfter you update your manifest file, the AlloyDB Omni operator starts\nthe upgrade process. To monitor the upgrade process, check the\n`DBCUpgradeInProgress` condition. \n\n```\nkubectl get dbclusters.alloydbomni.dbadmin.goog DB_CLUSTER_NAME -o yaml | yq '.status.conditions[] | select(.type == \"DBCUpgradeInProgress\")'\n```\n\nReplace the following variable:\n\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 provided when you created it. For more information, see [Install AlloyDB Omni on Kubernetes](/alloydb/omni/16.8.0/docs/deploy-kubernetes#create).\n\nWhile the process is in progress, the status is `true`. When the process is\ncomplete, the condition's status changes to `false`.\n\nTroubleshooting\n---------------\n\nIf you receive any failure messages during the upgrade process, see the\nfollowing sections:\n\n- [Pre-upgrade failures](#pre-upgrade-failures)\n- [Upgrade failures](#upgrade-failures)\n\n### Pre-upgrade failures\n\nIf you receive a pre-upgrade failure on your database cluster, then check the\nmessage and address the problem accordingly.\n\nIf you would like to bypass the pre-upgrade failure message, then you can enable\nthe `force-upgrade` annotation. \n\n```\nkubectl annotate dbclusters.alloydbomni.dbadmin.goog DB_CLUSTER_NAME upgrade.alloydbomni.dbadmin.google/force-upgrade=true\n```\n\nReplace the following variable:\n\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 provided when you created it. For more information, see [Install AlloyDB Omni on Kubernetes](/alloydb/omni/16.8.0/docs/deploy-kubernetes#create).\n\nAfter the upgrade process completes, set the `force-upgrade` annotation to\n`false`.\n\n### Upgrade failures\n\nDuring the automatic upgrade process, there are several points where it might\nfail in HA environments. For more information about each failure scenario and\nwhich subsequent actions the AlloyDB Omni operator takes, see the\nfollowing table.\n\n#### Fix primary and standby instances with different minor versions\n\nTo resolve this problem, choose one of the following options:\n\n- If the issue that caused the upgrade failure is fixed, retry the upgrade.\n\n To retry the upgrade, remove the upgrade's `start-time` annotation from\n your instance. After you remove the annotation, the\n AlloyDB Omni operator generates a new start time and re-initiates\n the upgrade process. \n\n ```\n kubectl annotate dbclusters.alloydbomni.dbadmin.goog DB_CLUSTER_NAME upgrade.alloydbomni.dbadmin.google/start-time-\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 provided when you created it. For more information, see [Install AlloyDB Omni on Kubernetes](/alloydb/omni/16.8.0/docs/deploy-kubernetes#create).\n- If the issue that caused the upgrade failure persists, then downgrade your\n instance to the previous AlloyDB Omni operator version.\n\n To downgrade your instance, follow the [upgrade process](#upgrade)\n and change the `databaseVersion` and `controlPlaneAgentsVersion` fields in\n the manifest file to the version you used before."]]
