Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Pelajari cara menetapkan jumlah maksimum instance container yang dapat digunakan untuk
layanan penayangan Knative Anda. Menentukan instance maksimum di
penayangan Knative memungkinkan Anda membatasi penskalaan layanan sebagai respons
terhadap permintaan masuk. Gunakan setelan ini sebagai salah satu cara untuk mengontrol biaya Anda atau untuk membatasi jumlah koneksi ke layanan pendukung seperti ke database.
Untuk informasi selengkapnya tentang cara penayangan Knative melakukan penskalaan otomatis pada
instance penampung, lihat
Penskalaan otomatis instance.
Mengatur dan memperbarui instance maksimum
Setiap perubahan konfigurasi akan
menghasilkan revisi baru. Revisi selanjutnya juga akan otomatis mendapatkan
setelan konfigurasi ini, kecuali jika Anda melakukan pembaruan eksplisit untuk mengubahnya.
Secara default, jumlah instance container dapat diskalakan tanpa batas. Anda dapat menetapkan batas atas untuk jumlah instance maksimum menggunakan konsolGoogle Cloud , atau Google Cloud CLI saat men-deploy layanan baru atau mengupdate layanan yang ada dan men-deploy revisi:
Klik Buat Layanan jika Anda mengonfigurasi
layanan baru yang akan di-deploy. Jika Anda mengonfigurasi
layanan yang sudah ada, klik layanan tersebut, lalu klik
Edit & Deploy New Revision.
Di bagian Setelan lanjutan, klik Penampung.
Di kolom berlabel Maximum number of
instances, tentukan jumlah maksimum instance
container yang diinginkan.
Klik Berikutnya untuk melanjutkan ke bagian berikutnya.
Di bagian Configure how this service is triggered,
pilih konektivitas yang ingin Anda gunakan untuk memanggil layanan.
Klik Create untuk men-deploy image ke layanan Knative dan tunggu deployment selesai.
Command line
Untuk layanan yang ada, tetapkan jumlah maksimum instance penampung dengan
menjalankan perintah gcloud run services update dengan parameter
--max-instances:
IMAGE_URL dengan referensi ke image container,
misalnya, gcr.io/cloudrun/hello.
MAX-VALUE dengan jumlah maksimum instance
container yang diinginkan. Tentukan default untuk menghapus semua setelan instance maksimum.
YAML
Anda dapat mendownload konfigurasi layanan yang ada ke dalam
file YAML dengan perintah gcloud run services describe menggunakan
tanda --format=export.
Kemudian, Anda dapat mengubah file YAML tersebut dan men-deploy
perubahan tersebut dengan perintah gcloud run services replace.
Anda harus memastikan bahwa Anda hanya mengubah atribut yang ditentukan.
Download konfigurasi layanan Anda ke dalam file bernama
service.yaml di ruang kerja lokal:
[[["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-07-31 UTC."],[],[],null,["# Setting a maximum number of container instances\n\nLearn how to set the maximum number of container instances that can be used for\nyour Knative serving service. Specifying maximum instances in\nKnative serving allows you to limit the scaling of your service in\nresponse to incoming requests. Use this setting as a way to control your costs\nor to limit the number of connections to a backing service, such as to a\ndatabase.\n\nFor more information on the way Knative serving autoscales\ncontainer instances, refer to\n[Instance autoscaling](/kubernetes-engine/enterprise/knative-serving/docs/instance-autoscaling).\n\nSetting and updating maximum instances\n--------------------------------------\n\nAny configuration change leads to the\ncreation of a new revision. Subsequent revisions will also automatically get\nthis configuration setting unless you make explicit updates to change it.\n\nBy default, the number of container instances can scale infinitely. You can set\nan upper bound for the maximum number of instances using the\nGoogle Cloud console, or the Google Cloud CLI when you deploy a new\n[service](/kubernetes-engine/enterprise/knative-serving/docs/deploying#service) or update an existing service and\ndeploy a [revision](/kubernetes-engine/enterprise/knative-serving/docs/deploying#revision): \n\n### Console\n\n\n1. Go to Knative serving in the Google Cloud console:\n\n [Go to Knative serving](https://console.cloud.google.com/kubernetes/run)\n2. Click **Create Service** if you are configuring a\n new service you are deploying to. If you are configuring an\n existing service, click on the service, then click\n **Edit \\& Deploy New Revision**.\n\n3. Under *Advanced settings* , click **Container**.\n\n4. In the field labelled *Maximum number of\n instances*, specify the desired maximum number of container\n instances.\n\n5. Click **Next** to continue to the next section.\n\n6. In the **Configure how this service is triggered** section,\n select which connectivity you would like to use to invoke the service.\n\n7. Click **Create** to deploy the image to Knative serving and wait\n for the deployment to finish.\n\n### Command line\n\n- For existing services, set the maximum number of container instances by\n running the `gcloud run services update` command with the\n [`--max-instances`](/sdk/gcloud/reference/run/services/update#--max-instances)\n parameter:\n\n ```bash\n gcloud run services update SERVICE --max-instances MAX-VALUE\n ```\n\n Replace:\n - \u003cvar translate=\"no\"\u003eSERVICE\u003c/var\u003e with the name of your service.\n - \u003cvar translate=\"no\"\u003eMAX-VALUE\u003c/var\u003e with the desired maximum number of container instances. Specify `default` to clear any maximum instance setting.\n- For new services, set the maximum number of container instances by running\n the `gcloud run deploy` command with the\n [`--max-instances`](/sdk/gcloud/reference/run/deploy#--max-instances)\n parameter:\n\n ```bash\n gcloud run deploy SERVICE --image=IMAGE_URL --max-instances MAX-VALUE\n ```\n\n Replace:\n - \u003cvar translate=\"no\"\u003eSERVICE\u003c/var\u003e with the name of your service.\n - \u003cvar translate=\"no\"\u003eIMAGE_URL\u003c/var\u003e with a reference to the container image, for example, `gcr.io/cloudrun/hello`.\n - \u003cvar translate=\"no\"\u003eMAX-VALUE\u003c/var\u003e with the desired maximum number of container instances. Specify `default` to clear any maximum instance setting.\n\n### YAML\n\n| **Caution:** Deploying configuration changes using YAML files replaces the configuration of your existing services. Since a YAML file completely overwrites all configurations, you should avoid using multiple methods to modify your services. For example, do not use YAML files in conjunction with the Google Cloud console or `gcloud` commands.\n\nYou can download the configuration of an existing service into a\nYAML file with the `gcloud run services describe` command by using the\n[`--format=export`](/sdk/gcloud/reference/run/services/describe) flag.\nYou can then modify that YAML file and deploy\nthose changes with the `gcloud run services replace` command.\nYou must ensure that you modify only the specified attributes.\n\n1. Download the configuration of your service into a file named\n `service.yaml` on local workspace:\n\n ```bash\n gcloud run services describe SERVICE --format export \u003e service.yaml\n ```\n\n Replace \u003cvar translate=\"no\"\u003eSERVICE\u003c/var\u003e with the name of your\n Knative serving service.\n2. In your local file, update the `autoscaling.knative.dev/maxScale:`\n attribute:\n\n ```yaml\n spec:\n template:\n metadata:\n annotations:\n autoscaling.knative.dev/maxScale: '\u003cvar translate=\"no\"\u003eMAX-INSTANCE\u003c/var\u003e' \n ```\n\n Replace\n - \u003cvar translate=\"no\"\u003eMAX-INSTANCE\u003c/var\u003e with the desired maximum number.\n3. Replace the service with its new configuration using the following command:\n\n ```bash\n gcloud run services replace service.yaml\n ```"]]
