使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
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
替换为日志的存储桶名称。
- 将
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
替换为日志的存储桶名称。
SOURCE_PROJECT
,并使用源项目部署 Cortex Framework Data Foundation。
- 将
YOUR_WORKER_POOL_NAME
替换为工作器池的名称。
- 将
REGION
替换为部署的区域。
如需详细了解可用区域,请参阅地理位置和区域。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-18。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-18。"],[[["\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)."]]