Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
O serviço do Cloud Deploy é executado como várias instâncias independentes e isoladas em diversos Google Cloud locais. O local em que você cria um
pipeline de entrega determina qual instância do Cloud Deploy armazena
e processa solicitações para esse pipeline.
A página Cloud Locations lista as regiões com suporte para cada produto do Google Cloud , incluindo o Cloud Deploy.
Quando o Cloud Deploy usa outros recursos de Google Cloud em um pipeline, ele os cria no mesmo local, se possível, incluindo buckets do Cloud Storage, por exemplo, que o Cloud Deploy usa para armazenar manifestos de configuração renderizados.
As instâncias do Cloud Deploy podem implantar aplicativos em locais diferentes daquele em que o Cloud Deploy está sendo executado. Esse recurso permite que os pipelines de entrega sejam implantados em várias regiões. No entanto, um determinado pipeline de entrega só pode ser acessado por uma única instância do Cloud Deploy.
As instâncias do Cloud Deploy operam de maneira independente. Dessa forma, uma falha em uma região não afeta uma instância em outra. Por esse motivo, se você estiver implantando apenas em uma única região, recomendamos (mas não exige) que você crie o pipeline no mesmo local do cluster de destino.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-17 UTC."],[[["\u003cp\u003eCloud Deploy operates through independent instances in various Google Cloud locations, with the delivery pipeline's location dictating the instance that manages its requests.\u003c/p\u003e\n"],["\u003cp\u003eDelivery pipelines, targets, releases, and rollouts must reside within the same region, but target GKE and GKE Enterprise clusters can be located in any region.\u003c/p\u003e\n"],["\u003cp\u003eCloud Deploy creates associated Google Cloud resources, like Cloud Storage buckets, within the same location as the delivery pipeline whenever feasible.\u003c/p\u003e\n"],["\u003cp\u003eCloud Deploy instances can deploy to locations beyond their own, enabling multi-region deployments, but a single pipeline remains confined to a single Cloud Deploy instance.\u003c/p\u003e\n"],["\u003cp\u003eChoosing a region can affect performance and billing due to data transfer variations between Google Cloud locations, and while it's not mandatory, it's recommended to create a pipeline in the same location as its target cluster when deploying to a single region.\u003c/p\u003e\n"]]],[],null,["# About Cloud Deploy regions\n\nThe Cloud Deploy service runs as multiple independent, isolated\ninstances in various Google Cloud locations. The location where you create a\ndelivery pipeline determines which Cloud Deploy instance stores\nand processes requests for that pipeline.\n\nThe [Cloud Locations page](https://cloud.google.com/about/locations) lists\nsupported regions for each Google Cloud product, including\nCloud Deploy.\n| **Note:** you must create targets, releases, and rollouts in the same region in which you created the delivery pipeline. (GKE and GKE Enterprise clusters represented by those targets, however, can be in any region.)\n\nWhen Cloud Deploy uses other Google Cloud resources for a\npipeline, it creates them in the same location if possible, including\nCloud Storage buckets, for example, which Cloud Deploy uses to\nstore rendered configuration manifests.\n\nCloud Deploy instances can deploy applications to locations other\nthan the one where Cloud Deploy is running. This capability allows\nyour delivery pipelines to deploy to multiple regions. However, a given delivery\npipeline is only accessible by a single Cloud Deploy instance.\n\nCloud Deploy instances operate independently, so a failure in one\nregion doesn't affect an instance in another. For this reason, if you are only\ndeploying to a single region, we recommended (but don't require) that you create\nyour pipeline in the same location as your target cluster.\n| **Note:** your choice of region can have an impact on performance and billing, because data transfers among Google Cloud locations can perform better or worse, depending on location."]]
