Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Harga Cloud Deploy
Dokumen ini berisi penjelasan mengenai detail penentuan harga Cloud Deploy.
Harga dasar
Cloud Deploy mengenakan biaya untuk pipeline pengiriman multi-target aktif.
Tabel harga
Item
Biaya pipeline pengiriman
Pertama aktif † multi-target † † pipeline pengiriman (per akun penagihan)
Tanpa biaya
Setiap pipeline pengiriman multi-target aktif tambahan
$5 per bulan penagihan
†pipeline pengiriman aktif adalah pipeline pengiriman untuk setidaknya satu release atau rollout yang
telah dibuat selama bulan penagihan. Jika release atau rollout
dibuat untuk pipeline pengiriman tersebut selama bulan tersebut, organisasi Anda akan
ditagih untuk pipeline pengiriman tersebut dengan tarif yang ditentukan dalam tabel harga di
halaman ini. Pipeline pengiriman yang tidak aktif tidak dikenakan biaya.
†† Pipeline pengiriman multi-target adalah
pipeline pengiriman yang mereferensikan lebih dari satu target. Pipeline ini dapat berupa pipeline
pengiriman dengan progres menggunakan lebih
dari satu target, atau pipeline pengiriman menggunakan
multi-target. Pipeline pengiriman yang menggunakan tepat satu target tidak dikenai biaya. Pipeline pengiriman yang menggunakan beberapa target yang diaktifkan kapan saja selama periode invoice dapat ditagih sebagai pipeline pengiriman multi-target.
Harga ditentukan berdasarkan nama pipeline pengiriman. Jika Anda menghapus pipeline, lalu membuat pipeline baru dengan nama yang sama, pipeline tersebut akan diperlakukan sebagai satu pipeline, untuk tujuan penagihan.
Jika Anda melakukan pembayaran dengan mata uang selain USD, yang berlaku adalah harga yang tercantum dalam mata uang Anda pada
SKU Cloud Platform.
Tagihan dari layanan Google Cloud lainnya
Selain tagihan pipeline per pengiriman dari Cloud Deploy, Anda juga dikenai biaya dari layanan lain yang digunakan Cloud Deploy:
Cloud Deploy menggunakan Cloud Build untuk rendering dan deployment. Aktivitas ini dilakukan di region yang sama dengan pipeline pengiriman. Anda akan ditagih untuk setiap aktivitas sesuai harga Cloud Build.
Secara default, Cloud Deploy menggunakan instance Cloud Build e2-medium.
Pipeline pengiriman Cloud Deploy dapat dikonfigurasi untuk menggunakan worker kustom Cloud Build, yang biayanya ditagihkan kepada Anda dengan harga worker kustom.
Cloud Deploy menggunakan bucket Cloud Storage untuk menyimpan kode sumber rendering dan manifes Kubernetes yang dirender. Bucket berada di region yang sama dengan pipeline pengiriman Cloud Deploy. Anda akan ditagih sesuai harga Cloud Storage regional.
Dengan model harga bayar sesuai penggunaan Google Cloud, Anda hanya membayar untuk layanan yang Anda gunakan. Hubungi tim penjualan kami untuk mendapatkan penawaran harga khusus bagi organisasi 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"]],[],[[["\u003cp\u003eCloud Deploy charges $5 per billing month for each active multiple-target delivery pipeline beyond the first one, which is free per billing account.\u003c/p\u003e\n"],["\u003cp\u003eA delivery pipeline is considered active and incurs charges if at least one release or rollout is created during the billing month.\u003c/p\u003e\n"],["\u003cp\u003eA multiple-target delivery pipeline, which is the type of pipeline that is charged, is defined as one that references more than one target, either through a progression or by using a multi-target setup.\u003c/p\u003e\n"],["\u003cp\u003eIn addition to Cloud Deploy's delivery pipeline charges, you will incur costs from other Google Cloud services it utilizes, including Cloud Build, Cloud Storage, Cloud Audit Logs, and Google Cloud Observability.\u003c/p\u003e\n"]]],[],null,["# Pricing\n\nCloud Deploy pricing\n====================\n\nThis document explains Cloud Deploy pricing details.\n\nBasic pricing\n-------------\n\nCloud Deploy charges for *active* multiple-target delivery\npipelines.\n\n\u003cbr /\u003e\n\nPricing table\n-------------\n\n^†^An active delivery pipeline is a delivery pipeline for\nwhich at least one [`release`](/deploy/docs/terminology#release) or [`rollout`](/deploy/docs/terminology#rollout)\nhas been created during the billing month. If a `release` or `rollout` is\ncreated for that delivery pipeline during that month, then your organization is\nbilled for that delivery pipeline at the rate specified in the pricing table on\nthis page. Delivery pipelines that aren't active don't incur the charge.\n\n^†^^†^ A multiple-target delivery pipeline is a\ndelivery pipeline that references more than one target. This may be a delivery\npipeline with a [progression](/deploy/docs/terminology#progression) using more\nthan one target, or a delivery pipeline using a\n[multi-target](/deploy/docs/terminology#multi-target). Delivery pipelines using\nexactly one target do not incur a charge. A delivery pipeline using multiple\ntargets that is activated at any time during an invoicing period can be charged\nas a multiple target delivery pipeline.\n\nPricing is determined based on delivery pipeline name. If you delete a pipeline\nand then create a new one with the same name, they're treated as a single\npipeline, for billing purposes.\n\n\nIf you pay in a currency other than USD, the prices listed in your currency on\n[Cloud Platform SKUs](https://cloud.google.com/skus/)\napply.\n| **Note:** Cloud Deploy uses Google Cloud services, and you're billed for use of those services.\n\nCharges from other Google Cloud services\n----------------------------------------\n\nIn addition to per-delivery-pipeline charges from Cloud Deploy, you\nincur charges from other services which Cloud Deploy depends on:\n\n- [Cloud Build](/build)\n\n Cloud Deploy uses Cloud Build for rendering and\n deploying. These activities are performed in the same region as the delivery\n pipeline. You're billed for each activity according to\n [Cloud Build's pricing](/build/pricing).\n\n By default, Cloud Deploy uses an e2-medium Cloud Build\n instance.\n\n Cloud Deploy delivery pipelines can be configured to use a\n Cloud Build custom worker, for which you're billed according to\n [custom worker pricing](/build/docs/custom-workers/custom-workers-pricing-quota).\n- [Cloud Storage](/storage)\n\n Cloud Deploy uses a Cloud Storage bucket to store rendering\n source code and rendered Kubernetes manifests. The bucket is located in the\n same regions as the Cloud Deploy delivery pipeline. You're billed\n at the regional [Cloud Storage pricing](/storage/pricing).\n- [Cloud Audit Logs](/logging/docs/audit)\n\n Cloud Deploy uses Cloud Audit Logs to create audit logs. You're\n billed at [Cloud Audit Logs pricing](/logging/docs/audit#pricing)\n- [Google Cloud Observability](/stackdriver)\n\n Cloud Deploy uses Cloud Logging for storing platform logs.\n\n You're billed at standard [Google Cloud Observability pricing](/stackdriver/pricing).\n\nWhat's next\n-----------\n\n- Read the [Cloud Deploy documentation](/deploy/docs).\n- Get started with [Cloud Deploy](/deploy/docs/deploy-app-gke).\n- Try the [Pricing calculator](/products/calculator).\n\n#### Request a custom quote\n\nWith Google Cloud's pay-as-you-go pricing, you only pay for the services you use. Connect with our sales team to get a custom quote for your organization.\n[Contact sales](/contact?direct=true)"]]
