[[["容易理解","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-04 (世界標準時間)。"],[[["\u003cp\u003eThe Upgrade API utilizes Kubernetes custom resources and the Kubernetes Resource Model (KRM) to manage tenant organization upgrade scheduling.\u003c/p\u003e\n"],["\u003cp\u003eThe GDC console or \u003ccode\u003ekubectl\u003c/code\u003e CLI are the recommended tools for interacting with the Upgrade API, but custom libraries can be used by referencing the API definition.\u003c/p\u003e\n"],["\u003cp\u003eThe Upgrade API endpoint is accessible via a specific URL structure, with the Management API server endpoint variable.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003ekubectl proxy\u003c/code\u003e can be used to access the Upgrade API's discovery document, which is located at a local URL after running the command.\u003c/p\u003e\n"],["\u003cp\u003eEach tenant organization has two maintenance windows, one for patch upgrades and one for minor upgrades, which can be managed through the GDC console and \u003ccode\u003ekubectl\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Overview of Upgrade API\n\nThe Upgrade API uses Kubernetes custom resources and relies on the Kubernetes\nResource Model (KRM). It manages the schedule for tenant organization upgrades.\n\nTo use the Upgrade API, we recommend that you use the GDC console or\n`kubectl` CLI. If your application needs to use your own libraries to call this\nAPI, use the following example and the\n[full API definition](/distributed-cloud/hosted/docs/latest/gdch/apis/service/upgrade/v1/upgrade-v1) to build\nyour requests.\n\nService endpoint and discovery document\n---------------------------------------\n\nThe API endpoint for the Upgrade API is\n`https://`\u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER_ENDPOINT\u003c/var\u003e`/apis/upgrade.gdc.goog/v1`,\nwhere \u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER_ENDPOINT\u003c/var\u003e is the endpoint of the\nManagement API server.\n\nUsing the `kubectl proxy` command, you can access that URL in your browser or\nwith a tool such as `curl` to get the discovery document for the Upgrade API.\nThe `kubectl proxy` command opens up a proxy to the Kubernetes API server on\nyour local machine. After that command is running, you can access the document at\nthe following URL: `http://127.0.0.1:8001/apis/upgrade.gdc.goog/v1`.\n\nExample upgrade MaintenanceWindow resource\n------------------------------------------\n\nYou can interact with maintenance windows using the GDC console and\n`kubectl` CLI in GDC. There are two maintenance windows\nfor every tenant organization, one for patch upgrades and the other for minor\nupgrades.\n\nThe following is an example of a `MaintenanceWindow` object configured to define\na maintenance window for GDC minor upgrades: \n\n apiVersion: upgrade.gdc.goog/v1\n kind: MaintenanceWindow\n metadata:\n name: minor-upgrade\n namespace: gpc-system\n spec:\n recurrence: FREQ=MONTHLY;BYSETPOS=1;BYDAY=SU\n timeWindow:\n end: \"2022-04-03T06:00:00Z\"\n start: \"2022-04-03T00:00:00Z\"\n upgradeType: MinorUpgrade"]]