You are currently viewing version 1.5 of the Apigee hybrid documentation.This version is end of life. You should upgrade to a newer version. For more information, seeSupported versions.

Now that you've configuredGoogle Cloud and the hybrid UI, and installed and configured theruntime, you're ready to see how it all works together.

This section walks you through the following:

1. Create a new API proxy in the Apigee UI using the API Proxy Wizard
2. Deploy your new proxy to your cluster with the UI

1. Create a new API proxy using the hybrid UI

This section describes how to create a new API proxy in the UI by using the API Proxy Wizard.

To create a simple API proxy using the API Proxy Wizard:

1. OpenApigee UI in a browser.
2. SelectDevelop > API Proxies in the main view.
3. From theEnvironment 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 inStep 5: Add an environment.

   The hybrid UI displays a list of API proxies for that environment. If you haven't created any proxies yet, the list is empty.

4. Click+Proxy in the upper right. The API Proxy Wizard starts.
5. SelectReverse proxy (most common), and clickNext.

   TheProxy details view is displayed.

6. Configure your proxy with the following settings:
   • Proxy Name: Enter "myproxy". The remaining steps in this section assume that this is your proxy's ID.
   • Proxy Base Path: Automatically set to "/myproxy". TheProxy Base 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.
   • (Optional) Description: Enter a description for your new API proxy, such as "Testing Apigee hybrid with a simple proxy".
   • 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.

   Your API proxy's details should look like the following:

   

7. ClickNext.
8. On thePolicies screen, selectPass through (no authorization) as the security option.
9. ClickNext.
10. On theSummary screen, clickCreate.

    Hybrid generates the proxy (sometimes referred to asthe proxy bundle):

    

    NOTE: In this case, the hybrid UI doesnot deploy the proxy to your cluster. You will do this inthe next step.
11. ClickGo to proxy list.

    Hybrid displays theProxies view, which displays a list of API proxies. The new proxy should be at the top of the list, with a gray status indicator, meaning that it has not yet been deployed.

2. Deploy your proxy to the cluster using the hybrid UI

After creating a new proxy, you must deploy it so that you can try it out. This sectiondescribes how to deploy your new proxy using the hybrid UI.

To deploy an API proxy in the hybrid UI:

1. In the hybrid UI, selectDevelop > API Proxies.

   Be sure the "test" environment is selected.

   The UI displays your new proxy in the proxies list:

   

2. Click on the "myproxy" proxy.

   The UI displays theAPI Proxies Overview tab for that proxy.

   Notice that underDeployments, theRevision column shows "Not deployed".

3. In theRevision column, expand the drop-down selector to choose the revision to deploy.

   The drop down list displays only "1" and "Undeploy".

4. Select "1"—the revision that you want to deploy—from the drop down list.

   The UI prompts you to confirm the deployment:

   

5. ClickDeploy.

   The UI begins the process of deploying revision 1 of your new proxy to the cluster.

   Note that deployment is not an instantaneous process. Hybrid's "eventually consistent" deployment model means that a new deployment will be rolled out to the cluster over a short period of time and not immediately.

While there areseveral ways to check thedeployment status of a proxy in the UI, the next two steps explain how to call the API proxy you just deployed and howto check the deployment status with a call to theApigee APIs.

3. Call the API proxy

When theUI indicates your proxy is deployed, you can try calling it using cURL or the REST client of your choice.For example:

1. Export your environment group's host alias to a variable:

   HOSTALIAS=your_host_alias

2. Call the API proxy:

   curl -k https://$HOSTALIAS/myproxy

   For example:

   curl -v -k https://apitest.acme.com/myproxy

   If the call succeeds, you will see the following output:

   Hello, Guest!

If you used a self-signed certificate and you get a TLS/SSL error, try these steps instead:

1. Export your environment group's host alias to a variable:

   HOSTALIAS=your_host_alias

2. Export the ingress host:

   export INGRESS_HOST=$(kubectl -n istio-system get service \  istio-ingressgateway -o jsonpath='{.status.loadBalancer.ingress[0].ip}')

3. Export the secure ingress port number:

   export SECURE_INGRESS_PORT=$(kubectl -n istio-system get \  service istio-ingressgateway -o jsonpath='{.spec.ports[?(@.name=="https")].port}')

4. Call the API proxy:

   curl  -H Host:$HOSTALIAS --resolve \$HOSTALIAS:$SECURE_INGRESS_PORT:$INGRESS_HOST  \  https://$HOSTALIAS:$SECURE_INGRESS_PORT/myproxy -k