透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Cloud Build 功能
本頁說明如何使用 Cloud Build 功能建構 Cortex Framework Data Foundation,包括在特定區域建構,或使用私人工作站集區。這些設定在資料隱私權、效能、安全性及自訂方面,都能帶來顯著優勢。最適合的做法取決於您的具體需求和應用程式性質。
在特定區域中建構
區域建構可確保資料保留在特定地理區域。這有助於您遵守當地資料隱私權法規、提高可用性及減少延遲。詳情請參閱「Cloud Build 位置」。
如要透過特定區域執行部署作業,請新增替代參數 _CLOUD_BUILD_REGION
和 --region
bash 參數,如下列指令所示:
gcloud builds submit \
--config=./cloudbuild.yaml \
--substitutions=_GCS_BUCKET=BUCKET_FOR_LOGS,_CLOUD_BUILD_REGION=REGION \
--region=REGION
更改下列內容:
- 將
BUCKET_FOR_LOGS
替換為記錄的 bucket 名稱。
- 將
REGION
替換為部署作業的區域。如要進一步瞭解可用區域,請參閱地理位置與地區。
使用私人工作站集區建構
使用私人工作站集區可為建構作業提供更安全的環境。私人集區為專屬的私人工作站集區,可自訂建構環境,包括存取私人網路中的資源。詳情請參閱私人集區總覽。
如要設定私人工作站,請新增 _WORKER_POOL_NAME
和對應的 _CLOUD_BUILD_REGION
參數,如下列指令所示:
gcloud builds submit \
--config=./cloudbuild.yaml
--substitutions=_GCS_BUCKET=BUCKET_FOR_LOGS,_WORKER_POOL_NAME='projects/SOURCE_PROJECT/locations/us-central1/workerPools/YOUR_WORKER_POOL_NAME',_CLOUD_BUILD_REGION=REGION \
--region=REGION
更改下列內容:
- 將
BUCKET_FOR_LOGS
替換為記錄的 bucket 名稱。
SOURCE_PROJECT
,並與 Cortex Framework 資料基礎部署作業的來源專案建立關聯。
YOUR_WORKER_POOL_NAME
替換為工作站集區的名稱。
- 將
REGION
替換為部署作業的區域。如要進一步瞭解可用區域,請參閱地理位置與地區。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-09-04 (世界標準時間)。
[[["容易理解","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\u003eThis document outlines optional configurations for building the Cortex Framework Data Foundation using Cloud Build features to enhance data privacy, performance, security, and customization.\u003c/p\u003e\n"],["\u003cp\u003eDeployments can be run through a user-created service account, specified with the \u003ccode\u003e_BUILD_ACCOUNT\u003c/code\u003e substitution parameter, allowing a deployment process without direct resource access.\u003c/p\u003e\n"],["\u003cp\u003eYou can ensure data remains within a specific geographical boundary by utilizing the regional building feature, activated by adding the \u003ccode\u003e_CLOUD_BUILD_REGION\u003c/code\u003e substitution parameter with the \u003ccode\u003e--region\u003c/code\u003e parameter.\u003c/p\u003e\n"],["\u003cp\u003eA private worker pool can be configured for a more secure build environment, enabling customization and access to private network resources, by specifying the \u003ccode\u003e_WORKER_POOL_NAME\u003c/code\u003e and \u003ccode\u003e_CLOUD_BUILD_REGION\u003c/code\u003e parameters.\u003c/p\u003e\n"]]],[],null,["# Cloud Build features\n====================\n\nThis page describes some optional configurations to build the\nCortex Framework Data Foundation with Cloud Build features,\nsuch as building in a specific region\nor using a private worker pool. These configurations offer significant benefits\nin terms of data privacy, performance, security, and customization. The best\napproach depends on your specific requirements and the nature of your application.\n\nBuild in a specific region\n--------------------------\n\nRegional Building ensures that your data remains within a specific geographic\nregion. This can help you to comply with local data privacy regulation,\navailability and latency reduction. For more information, see\n[Cloud Build locations](/build/docs/locations).\n\nTo run the deployment through a specific [region](/build/docs/locations#selecting_the_region),\nadd the substitution parameter `_CLOUD_BUILD_REGION` with `--region` bash parameter,\nas the following command: \n\n gcloud builds submit \\\n --config=./cloudbuild.yaml \\\n --substitutions=_GCS_BUCKET=\u003cvar translate=\"no\"\u003eBUCKET_FOR_LOGS\u003c/var\u003e,_CLOUD_BUILD_REGION=\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e \\\n --region=\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eBUCKET_FOR_LOGS\u003c/var\u003e with the bucket name for the logs.\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e with the region for your deployment. For more information about available regions, see [Geography and regions](/docs/geography-and-regions).\n\nBuild with a private worker pool\n--------------------------------\n\nUsing a [private worker pool](/build/docs/private-pools/run-builds-in-private-pool)\nprovides a more secure environment for your builds.\nPrivate pools are private, dedicated pools of workers that offer\ncustomization over the build environment, including the ability to access\nresources in a private network. For more information, see\n[Private pools overview](/build/docs/private-pools/private-pools-overview).\n\nTo configure a private worker, add the `_WORKER_POOL_NAME` with corresponding\n`_CLOUD_BUILD_REGION` parameter, as the following command: \n\n gcloud builds submit \\\n --config=./cloudbuild.yaml\n --substitutions=_GCS_BUCKET=\u003cvar translate=\"no\"\u003eBUCKET_FOR_LOGS\u003c/var\u003e,_WORKER_POOL_NAME='projects/\u003cvar translate=\"no\"\u003eSOURCE_PROJECT\u003c/var\u003e/locations/us-central1/workerPools/\u003cvar translate=\"no\"\u003eYOUR_WORKER_POOL_NAME\u003c/var\u003e',_CLOUD_BUILD_REGION=\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e \\\n --region=\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eBUCKET_FOR_LOGS\u003c/var\u003e with the bucket name for the logs.\n- \u003cvar translate=\"no\"\u003eSOURCE_PROJECT\u003c/var\u003e with the source project for Cortex Framework Data Foundation deployment.\n- \u003cvar translate=\"no\"\u003eYOUR_WORKER_POOL_NAME\u003c/var\u003e with the name for your worker pool.\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e with the region for your deployment. For more information about available regions, see [Geography and regions](/docs/geography-and-regions)."]]