Topik ini menjelaskan cara mengubah IP instance Apigee dengan memperbarui VM secara manual.
Ringkasan
Saat instance Apigee
dihapus
lalu dibuat
lagi, alamat IP akan dibuat untuk instance yang baru dibuat. Misalnya, parameter
instance tertentu, seperti cidrRange dan networking, tidak dapat diubah. Oleh karena itu, jika ingin mengubah
parameter ini, Anda harus menghapus instance dan membuatnya kembali dengan konfigurasi yang diinginkan.
Dalam kebanyakan kasus, saat Anda membuat ulang instance, IP instance yang sama akan dipilih, tetapi mendapatkan IP yang sama tidak dijamin. VM yang merutekan traffic dari load balancer ke
IP pribadi Apigee masih memiliki alamat IP lama; oleh karena itu, jika IP instance
baru dibuat, Anda harus memperbarui VM secara manual dengan IP baru.
Mengubah IP instance
Untuk memperbarui VM dengan IP instance baru, ikuti langkah-langkah berikut:
Di Google Cloud konsol, buka halaman Virtual Machines>Instance templates.
Klik template instance Apigee (template yang ingin Anda salin dan perbarui).
Klik Buat yang Serupa.
Di kolom Nama, berikan nama baru untuk template. Misalnya, Anda dapat menambahkan akhiran seperti "v2" di
akhir nama asli.
Di bagian Opsi lanjutan, klik tab Pengelolaan.
Scroll ke bawah ke bagian Metadata (Opsional) dan cari key-value pair yang berisi kunci
ENDPOINT. Ubah nilai endpoint agar cocok dengan IP instance baru. Gunakan IP Anda, bukan yang ditampilkan di screenshot:
Klik Buat untuk membuat template.
Di konsol Google Cloud , buka halaman Instance groups.
Di kolom Name pada daftar, klik nama grup instance Apigee yang ingin Anda ubah.
Klik Edit untuk mengubah grup instance ini.
Di bagian Instance template, pilih template instance baru (yang baru saja Anda buat).
Klik Simpan.
Di bagian atas halaman, klik Update bertahap.
Biarkan semua default/preset apa adanya, lalu klik Update.
VM baru memerlukan waktu beberapa menit untuk aktif, dan VM lama akan dimatikan dan
dihapus. Setelah VM baru aktif, semua traffic API akan dilanjutkan seperti biasa.
[[["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-05 UTC."],[[["\u003cp\u003eThis content pertains to Apigee, excluding Apigee hybrid, and is specifically for organizations with VPC peering enabled.\u003c/p\u003e\n"],["\u003cp\u003eWhen an Apigee instance is deleted and recreated, a new IP address may be generated, requiring manual updating of the VMs.\u003c/p\u003e\n"],["\u003cp\u003eChanging certain immutable parameters of an Apigee instance, like \u003ccode\u003ecidrRange\u003c/code\u003e and networking, necessitates deleting and recreating the instance.\u003c/p\u003e\n"],["\u003cp\u003eTo update VMs with a new instance IP, create a new instance template, modify the \u003ccode\u003eENDPOINT\u003c/code\u003e metadata to reflect the new IP, and then apply this template to the instance group via a rolling update.\u003c/p\u003e\n"],["\u003cp\u003eAfter a rolling update is initiated, new VMs will take a few minutes to become operational, and old VMs will be shut down, resuming normal API traffic upon completion.\u003c/p\u003e\n"]]],[],null,["# Changing instance IPs\n\n*This page\napplies to **Apigee** , but not to **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\n| **Important:** This topic only applies to organizations that were created with VPC peering enabled. See also [Apigee networking options](/apigee/docs/api-platform/get-started/networking-options).\n\n\nThis topic explains how to change the IP of an Apigee instance by manually updating the\nVMs.\n\nOverview\n--------\n\n\nWhen an Apigee instance is\n[deleted](https://cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations.instances/delete)\nand then [created](https://cloud.google.com/apigee/docs/reference/apis/apigee/rest/v1/organizations.instances/create)\nagain, an IP address is generated for the newly created instance. For example, certain instance\nparameters, such as cidrRange and networking, are immutable. Therefore, if you want to change\nthese parameters, you must delete the instance and recreate it with the desired configuration.\n\n\nIn most cases, when you recreate an instance, the same instance IP is selected, but getting the\nsame IP is not guaranteed. The VMs that are routing traffic from the load balancer to\nApigee's private IP still have the old IP address; therefore, in cases where a new instance\nIP is generated, you have to manually update the VMs with the new IP.\n\nChanging the instance IP\n------------------------\n\n\nTo update the VMs with a new instance IP, follow these steps:\n\n1. In the Google Cloud console, go to the **Virtual Machines** \\\u003e **Instance templates** page.\n\n [Go to Instance templates](https://console.cloud.google.com/compute/instanceTemplates/list)\n2. Click on the Apigee instance template (the template that you want to copy and update).\n3. Click **Create Similar**.\n4. In the **Name** field, provide a new name for the template. For example, you might add a suffix like \"v2\" at the end of the original name.\n5. Under **Advanced options** , click the **Management** tab.\n6. Scroll down to the **Metadata (Optional)** section and look for the key value pair containing the **ENDPOINT** key. Change the value of the endpoint to match the new instance IP. Use your IP, not the one shown in the screenshot:\n\n7. Click **Create** to create the template.\n8. In the Google Cloud console, go to the **Instance groups** page.\n\n [Go to Instance groups](https://console.cloud.google.com/compute/instanceGroups/list)\n9. Under the **Name** column of the list, click the name of the Apigee instance group that you wish to modify.\n10. Click **Edit** to modify this instance group.\n11. Under **Instance template**, select the new instance template (the one you just created).\n12. Click **Save**.\n13. At the top of the page, click **Rolling update**.\n14. Leave all the defaults/presets as-is and click **Update**.\n15. It takes a few minutes for the new VMs to come up, and the old VMs will be shut down and removed. Once the new VMs are up, all API traffic will resume normally."]]
