[[["容易理解","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 (世界標準時間)。"],[[["\u003cp\u003eCloud Deploy utilizes Skaffold, accessed through Cloud Build, to render and deploy application manifests.\u003c/p\u003e\n"],["\u003cp\u003eCloud Deploy uses a custom image that includes a Skaffold LTS version, and the version number of the image corresponds to the Skaffold version number.\u003c/p\u003e\n"],["\u003cp\u003eYou can use the \u003ccode\u003egcloud deploy releases create\u003c/code\u003e command with the \u003ccode\u003e--skaffold-version\u003c/code\u003e flag to specify which supported Skaffold version to use for a given release.\u003c/p\u003e\n"],["\u003cp\u003eA new default Skaffold version is selected every 90 days, and each version is supported for 12 months, followed by a 60-day maintenance period.\u003c/p\u003e\n"],["\u003cp\u003eThe current Skaffold version being used by Cloud Deploy for a given release can be found by using the command: \u003ccode\u003egcloud deploy releases describe\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Manage Skaffold versions\n\nCloud Deploy uses [Skaffold](/skaffold), through Cloud Build,\nto deploy your application by rendering and deploying manifests.\n\nThe page describes how Cloud Deploy selects what version of Skaffold\nto use. This page also includes information about the following:\n\n- [How often the Skaffold version changes](#how_select)\n- [How to find out the current version](#find_out_the_skaffold_version_associated_with_a_release)\n- [How long each version is supported](#skaffold_version_deprecation_and_maintenance_policy)\n\nWhat version of Skaffold does Cloud Deploy use?\n-----------------------------------------------\n\nCloud Deploy performs its operations using a custom image, which\nincludes a Skaffold LTS version. Each supported version of Skaffold is listed in the\n[table](#supported_versions) in this document, linked to the repository of all\nCloud Deploy images. The version number of each Cloud Deploy\nimage corresponds to the Skaffold version number.\n| **Note:** the Skaffold version associated with a release is used for the entire lifecycle of that release, and cannot be changed during that lifetime. The release lifecycle consists of all render, deploy, and other jobs on that release. This includes up to deployment into the final target in the progression, and beyond (rollbacks or redeployments).\n\n### Supported versions\n\nEach version in this table links to a repository in Artifact Registry. In that\nrepository, look for the most recent date for the latest version or for the\nversion you want. The repository linked is in the `us-central1` region, but\nthese images are available in each region where Cloud Deploy is\navailable. The image that gets used is in the region where the delivery\npipeline was created.\n\nCloud Deploy uses the latest patch release for each supported\nSkaffold version. We announce support for new versions, including specific\nSkaffold version patches, in the [release notes](/deploy/docs/release-notes).\n\n### Preview version\n\nYou can use the [Cloud Deploy Preview image](https://console.cloud.google.com/artifacts/docker/cd-image-prod/us-central1/cd-image/cd?project=cd-image-prod),\nwhich includes preview features.\n\nThe Skaffold version in the preview image can be updated at any time, and\ndoesn't follow a regular release schedule. We recommend you not use the preview\nversion for production workloads.\n\nThe preview version is in the same repository as the supported versions. Look\nfor images with a tag that begins with `skaffold_preview`.\n\nSome preview features require the Cloud Deploy preview image. For\nthese features, Cloud Deploy uses that preview version\nwithout you having to do anything. If you try to select a different Skaffold\nversion when you create a release using a preview feature, the command fails.\n\n### Find out the Skaffold version associated with a release\n\nYou can find the version Cloud Deploy is using at any given time by\nrunning the following command: \n\n gcloud deploy releases describe \u003cvar label=\"release\" translate=\"no\"\u003eRELEASE\u003c/var\u003e \\\n --delivery-pipeline=\u003cvar label=\"pipeline\" translate=\"no\"\u003eDELIVERY_PIPELINE\u003c/var\u003e \\\n --region=\u003cvar label=\"region\" translate=\"no\"\u003eREGION\u003c/var\u003e\n\nThe version is shown in the `skaffoldVersion` attribute in the output.\n\n### Choose what version of Skaffold to use\n\nYou can use any [supported](#supported_versions) version of Skaffold.\nTo select the version that you want to use, include the\n[`--skaffold-version`](https://cloud.google.com/sdk/gcloud/reference/deploy/releases/create#--skaffold-version)\nflag on the `gcloud deploy releases create` command: \n\n gcloud deploy releases create \u003cvar label=\"release name\" translate=\"no\"\u003eRELEASE_NAME\u003c/var\u003e \\\n --delivery-pipeline=\u003cvar label=\"pipeline name\" translate=\"no\"\u003ePIPELINE_NAME\u003c/var\u003e \\\n --skaffold-version=\u003cvar label=\"skaffold\" translate=\"no\"\u003eSKAFFOLD_VERSION\u003c/var\u003e \\\n --region=\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e\n\nWhere '\u003cvar label=\"skaffold\" translate=\"no\"\u003eSKAFFOLD_VERSION\u003c/var\u003e' is the (supported) version\nof Skaffold to use for this release. The version should be in the form of\n`n.nn` for a numbered version, or `skaffold_preview` to use the [preview version](#preview_version).\n\nFor example, the following command selects Skaffold version `2.8`: \n\n gcloud deploy releases create release-001 \\\n --delivery-pipeline=my-pipeline \\\n --skaffold-version=2.8 \\\n --region=us-central1\n\nAnd this command selects the Skaffold [preview version](#preview_version): \n\n gcloud deploy releases create release-001 \\\n --delivery-pipeline=my-pipeline \\\n --skaffold-version=skaffold_preview \\\n --region=us-central1\n\nHow Cloud Deploy selects new versions\n-------------------------------------\n\nA new version of Skaffold is selected every 90 days. At the end of that 90-day\ncycle, Google Cloud adds support for a new Skaffold version. You can now use\nthat version with Cloud Deploy. It becomes the default version used\nto create and manage all releases for the next 90-day cycle.\n\nCloud Deploy [release notes](/deploy/docs/release-notes) are updated to\nannounce each newly supported release.\n\nSkaffold version deprecation and maintenance policy\n---------------------------------------------------\n\nSkaffold versions are supported for 12 months, with a 60-day maintenance period.\nThis maintenance period means that releases tied to a version are still\nsupported for 60 days after support for that version has expired. You can\nstill create rollouts from those releases, but you can't create *releases* using\na Skaffold version that's in the maintenance period.\n\nAfter the 60-day maintenance period, the Skaffold version is no longer\nsupported. You can no longer create rollouts from a release that uses the\nunsupported version. However, all data associated with the release remains.\n\nWhat's next\n-----------\n\n- Read more about [integrating Cloud Deploy with other systems](/deploy/docs/integrating).\n\n- [Find out more](/deploy/docs/set-up-skaffold) about how Skaffold works with\n Cloud Deploy and how to make it work well for you.\n\n- The document [Managing manifests in Cloud Deploy](/deploy/docs/using-skaffold/managing-manifests)\n describes more about how you can use Skaffold, including with other, third-party\n manifest-management tools."]]
