Dari menu drop-down Environment, pilih lingkungan tempat Anda ingin membuat proxy API baru. Bagian ini mengasumsikan bahwa nama lingkungan adalah "test". Anda telah membuat setidaknya satu lingkungan di Langkah 5: Menambahkan lingkungan.
UI hybrid menampilkan daftar proxy API untuk lingkungan tersebut. Jika Anda belum membuat proxy, daftar akan kosong.
Klik +Proxy di kanan atas. Wizard Proxy API akan dimulai.
Pilih Reverse proxy (paling umum), lalu klik Berikutnya.
Tampilan Detail proxy akan ditampilkan.
Konfigurasikan proxy dengan setelan berikut:
Nama Proxy: Masukkan "myproxy". Langkah-langkah yang tersisa di bagian ini mengasumsikan bahwa ini adalah ID proxy Anda.
Proxy Base Path: Otomatis disetel ke "/myproxy". Jalur Dasar Proxy adalah bagian dari URL yang digunakan untuk membuat permintaan ke API Anda. Edge menggunakan URL untuk
mencocokkan dan merutekan permintaan masuk ke proxy API yang sesuai.
(Opsional) Deskripsi: Masukkan deskripsi untuk proxy API baru Anda, seperti "Menguji Apigee hybrid dengan proxy sederhana".
Target (API yang Ada): Masukkan "https://mocktarget.apigee.net". Ini menentukan URL target yang dipanggil Apigee pada permintaan ke proxy API. Layanan mocktarget dihosting di Apigee dan menampilkan data sederhana. Anda tidak memerlukan kunci API atau token akses.
Detail proxy API Anda akan terlihat seperti berikut:
Klik Berikutnya.
Di layar Kebijakan, pilih Pass through (tanpa otorisasi) sebagai
opsi keamanan.
Klik Berikutnya.
Di layar Ringkasan, klik Buat.
Hybrid membuat proxy (terkadang disebut sebagai paket proxy):
Klik Buka daftar proxy.
Hybrid menampilkan tampilan Proxy, yang menampilkan daftar proxy API. Proxy baru akan berada di bagian atas daftar, dengan indikator status abu-abu, yang berarti proxy tersebut belum di-deploy.
2. Men-deploy proxy ke cluster menggunakan UI hybrid
Setelah membuat proxy baru, Anda harus men-deploynya agar dapat mencobanya. Bagian ini menjelaskan cara men-deploy proxy baru menggunakan UI campuran.
Untuk men-deploy proxy API di UI campuran:
Di UI campuran, pilih Develop > API Proxies.
Pastikan lingkungan "pengujian" dipilih.
UI akan menampilkan proxy baru Anda dalam daftar proxy:
Klik proxy "myproxy".
UI menampilkan tab Ringkasan Proxy API untuk proxy tersebut.
Perhatikan bahwa di bagian Deployments, kolom Revision menampilkan
"Not deployed".
Di kolom Revision, luaskan pemilih drop-down untuk memilih revisi yang akan di-deploy.
Daftar drop-down hanya menampilkan "1" dan "Undeploy".
Pilih "1"—revisi yang ingin Anda deploy—dari menu drop-down.
UI akan meminta Anda untuk mengonfirmasi deployment:
Klik Deploy.
UI akan memulai proses deployment revisi 1 proxy baru Anda ke cluster.
Perhatikan bahwa deployment bukan proses yang instan. Model deployment "eventually consistent"
Hybrid berarti deployment baru akan diluncurkan ke cluster dalam jangka waktu
singkat dan tidak langsung.
Meskipun ada beberapa cara untuk memeriksa
status deployment proxy di UI, dua langkah berikutnya menjelaskan cara memanggil proxy API
yang baru saja Anda deploy dan cara
memeriksa status deployment dengan panggilan ke Apigee API.
3. Memanggil proxy API
Ikuti langkah-langkah di bawah, bergantung pada apakah Anda dapat memperbarui data DNS nama host yang digunakan untuk membuat grup lingkungan atau tidak.
Jika Anda tidak dapat memperbarui DNS nama host
Ikuti langkah-langkah berikut jika nama host grup lingkungan Anda tidak terdaftar, atau Anda tidak dapat
memperbarui data DNS-nya. Pada langkah-langkah ini, Anda akan mendapatkan IP masuk dan menggunakannya langsung dalam panggilan cURL
dengan flag --resolve:
Mengekspor IP ingress:
export INGRESS_IP=$(kubectl -n istio-system get service \
istio-ingressgateway -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
Mengekspor nomor port masuk yang aman:
export SECURE_INGRESS_PORT=$(kubectl -n istio-system get \
service istio-ingressgateway -o jsonpath='{.spec.ports[?(@.name=="https")].port}')
Ikuti langkah-langkah berikut jika nama host yang Anda gunakan saat membuat grup lingkungan terdaftar dan Anda dapat memperbarui data DNS-nya untuk mengarah ke IP masuk eksternal:
Ekspor IP eksternal ingress ke variabel:
export INGRESS_IP=$(kubectl -n istio-system get service \
istio-ingressgateway -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
Pastikan variabel menyimpan alamat IP. Contoh:
echo $INGRESS_IP
34.118.196.202
Gunakan alamat IP ini untuk memperbarui data DNS (biasanya data A atau CNAME) di registrar atau penyedia DNS Anda. Anda
mungkin harus menunggu hingga satu jam agar perubahan data DNS diterapkan.
[[["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-08-21 UTC."],[[["\u003cp\u003eThis guide explains how to create a new API proxy in the Apigee hybrid UI using the API Proxy Wizard, including setting the proxy name, base path, and target.\u003c/p\u003e\n"],["\u003cp\u003eAfter creating the proxy, it details the steps to deploy the newly created proxy to the cluster via the hybrid UI, noting that deployment is not instantaneous.\u003c/p\u003e\n"],["\u003cp\u003eThe document provides instructions on how to call the API proxy after deployment, with separate methods for those who can and cannot update their DNS records.\u003c/p\u003e\n"],["\u003cp\u003eThe guide assumes the use of version 1.7 of the documentation, which is end-of-life and recommends upgrading to a newer supported version.\u003c/p\u003e\n"]]],[],null,["# Create and deploy a new API proxy\n\n| You are currently viewing version 1.7 of the Apigee hybrid documentation. **This version is end of life.** You should upgrade to a newer version. For more information, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n\nNow that you've configured and the hybrid UI, and installed and configured the\nruntime, you're ready to see how it all works together.\n\nThis section walks you through the following:\n\n1. **[Create a new API proxy](#create-proxy)** in the Apigee UI using the API Proxy Wizard\n2. **[Deploy your new proxy](#deploy)** to your cluster with the UI\n\n1. Create a new API proxy using the hybrid UI\n---------------------------------------------\n\nThis section describes how to create a new API proxy in the UI by using the API Proxy Wizard.\n\n**To create a simple API proxy using the API Proxy Wizard:**\n\n1. Open [Apigee UI](https://apigee.google.com) in a browser.\n2. Select **Develop \\\u003e API Proxies** in the main view.\n3. From the **Environment** drop-down list, select the environment in which you want to create a new API proxy. This section assumes the name of the environment is \"test\". You created at least one environment in [Step 5: Add an environment](/apigee/docs/hybrid/v1.7/precog-add-environment).\n\n The hybrid UI displays a list of API proxies for that environment. If you haven't created any\n proxies yet, the list is empty.\n4. Click **+Proxy** in the upper right. The API Proxy Wizard starts.\n5. Select **Reverse proxy** (most common), and click **Next** .\n\n The **Proxy details** view is displayed.\n6. Configure your proxy with the following settings:\n - **Proxy Name:** Enter \"myproxy\". The remaining steps in this section assume that this is your proxy's ID.\n - **Proxy Base Path:** Automatically set to \"/myproxy\". The **Proxy Base\n Path** is part of the URL used to make requests to your API. Edge uses the URL to match and route incoming requests to the proper API proxy.\n - (Optional)**Description:** Enter a description for your new API proxy, such as \"Testing Apigee hybrid with a simple proxy\".\n - **Target (Existing API):** Enter \"https://mocktarget.apigee.net\". This defines the target URL that Apigee invokes on a request to the API proxy. The mocktarget service is hosted at Apigee and returns simple data. It requires no API key or access token.\n\n Your API proxy's details should look like the following:\n\n7. Click **Next**.\n8. On the **Policies** screen, select **Pass through (no authorization)** as the security option.\n9. Click **Next**.\n10. On the **Summary** screen, click **Create** .\n\n Hybrid generates the proxy (sometimes referred to as *the proxy bundle*):\n\n | **NOTE:** In this case, the hybrid UI does *not* deploy the proxy to your cluster. You will do this in [the next step](#deploy).\n11. Click **Go to proxy list** .\n\n Hybrid displays the **Proxies** view, which displays a list of API proxies. The\n new proxy should be at the top of the list, with a gray status indicator, meaning that it has\n not yet been deployed.\n\n2. Deploy your proxy to the cluster using the hybrid UI\n-------------------------------------------------------\n\nAfter creating a new proxy, you must deploy it so that you can try it out. This section\ndescribes how to deploy your new proxy using the hybrid UI.\n\n**To deploy an API proxy in the hybrid UI:**\n\n1. In the hybrid UI, select **Develop \\\u003e API Proxies** .\n\n Be sure the \"test\" environment is selected.\n\n The UI displays your new proxy in the proxies list:\n\n2. Click on the \"myproxy\" proxy.\n\n The UI displays the **API Proxies Overview** tab for that proxy.\n\n Notice that under **Deployments** , the **Revision** column shows\n \"Not deployed\".\n3. In the **Revision** column, expand the drop-down selector to choose the revision to deploy.\n\n The drop down list displays only \"1\" and \"Undeploy\".\n4. Select \"1\"---the revision that you want to deploy---from the drop down list.\n\n The UI prompts you to confirm the deployment:\n\n5. Click **Deploy** .\n\n The UI begins the process of deploying revision 1 of your new proxy to the cluster.\n\n Note that deployment is not an instantaneous process. Hybrid's \"eventually consistent\"\n deployment model means that a new deployment will be rolled out to the cluster over a short\n period of time and not immediately.\n\nWhile there are [several ways](/apigee/docs/api-platform/deploy/ui-deploy-overview#viewing-deployment-status) to check the\ndeployment status of a proxy in the UI, the next two steps explain how to call the API proxy\nyou just deployed and how\nto check the deployment status with a call to the [Apigee APIs](/apigee/docs/reference/apis/apigee/rest).\n\n3. Call the API proxy\n---------------------\n\n\nFollow the steps below, depending on whether or not you can update the DNS record of the hostname you\nused to create the [environment group](/apigee/docs/hybrid/v1.7/precog-add-environment).\n\n### If you are unable to update your hostname's DNS\n\n\nFollow these steps if your [environment group](/apigee/docs/hybrid/v1.7/precog-add-environment) hostname is not registered, or you are not able\nto update its DNS record. In these steps, you get the ingress IP and use it directly in a cURL call\nwith the `--resolve` flag:\n\n1. Export the ingress IP: \n\n ```\n export INGRESS_IP=$(kubectl -n istio-system get service \\\n istio-ingressgateway -o jsonpath='{.status.loadBalancer.ingress[0].ip}')\n ```\n2. Export the secure ingress port number: \n\n ```\n export SECURE_INGRESS_PORT=$(kubectl -n istio-system get \\\n service istio-ingressgateway -o jsonpath='{.spec.ports[?(@.name==\"https\")].port}')\n ```\n3. Export your [environment group](/apigee/docs/hybrid/v1.7/precog-add-environment)'s host alias to a variable: \n\n ```\n export HOSTALIAS=your_host_alias\n ```\n4. Call the API proxy. The `--resolve` flag on cURL allows you to directly specify the ingress IP: \n\n ```\n curl -H Host:$HOSTALIAS --resolve \\\n $HOSTALIAS:$SECURE_INGRESS_PORT:$INGRESS_IP \\\n https://$HOSTALIAS:$SECURE_INGRESS_PORT/myproxy -k\n ```\n\n### If you are able to update your hostname's DNS\n\n\nFollow these steps if the hostname you used when you created the [environment group](/apigee/docs/hybrid/v1.7/precog-add-environment) is registered\nand you can update its DNS record to point to the external ingress IP:\n\n1. Export the external IP of the ingress to a variable: \n\n ```\n export INGRESS_IP=$(kubectl -n istio-system get service \\\n istio-ingressgateway -o jsonpath='{.status.loadBalancer.ingress[0].ip}')\n ```\n2. Check that the variable holds the IP address. For example: \n\n ```\n echo $INGRESS_IP\n 34.118.196.202\n ```\n3. Use this IP address to update your DNS record (usually an A or CNAME record) at your registrar or DNS provider. You may have to wait up to an hour for the DNS record change to propagate.\n4. Export your [environment group](/apigee/docs/hybrid/v1.7/precog-add-environment)'s host alias to a variable: \n\n ```\n export HOSTALIAS=your_host_alias\n ```\n5. Call the API proxy: \n\n ```\n curl -k https://$HOSTALIAS/myproxy\n ```\n\n\n For example: \n\n ```\n curl -v -k https://apitest.acme.com/myproxy\n ```\n\n If the call succeeds, you will see the following output: \n\n ```text\n Hello, Guest!\n ```\n\n*[Google Cloud]: Google Cloud"]]
