Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Layanan Cloud Deploy berjalan sebagai beberapa instance independen dan terisolasi di berbagai lokasi Google Cloud . Lokasi tempat Anda membuat
pipeline pengiriman menentukan instance Cloud Deploy yang menyimpan
dan memproses permintaan untuk pipeline tersebut.
Halaman Lokasi Cloud mencantumkan
region yang didukung untuk setiap Google Cloud produk, termasuk
Cloud Deploy.
Saat Cloud Deploy menggunakan resource Google Cloud lain untuk
pipeline, Cloud Deploy akan membuatnya di lokasi yang sama jika memungkinkan, termasuk
bucket Cloud Storage, misalnya, yang digunakan Cloud Deploy untuk
menyimpan manifes konfigurasi yang dirender.
Instance Cloud Deploy dapat men-deploy aplikasi ke lokasi selain lokasi tempat Cloud Deploy berjalan. Kemampuan ini memungkinkan pipeline pengiriman Anda di-deploy ke beberapa region. Namun, pipeline pengiriman
tertentu hanya dapat diakses oleh satu instance Cloud Deploy.
Instance Cloud Deploy beroperasi secara independen, sehingga kegagalan di satu
region tidak memengaruhi instance di region lain. Oleh karena itu, jika Anda hanya men-deploy ke satu region, sebaiknya (tetapi tidak wajib) buat pipeline di lokasi yang sama dengan cluster target Anda.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-03 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."]]
