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

You can now try out the hybrid UI and add a new environment. Without an environment, you havenowhere to deploy your API proxies. Additionally, if you don’t create an environment as describedin this section, then several steps in the hybrid runtime installation process will fail.

The hybrid UI includes functionality that lets you do the following in a hybrid-enabled organization:

• Create, edit, and delete environments
• Assign environment-level access control to GCP project users
• Deploy and undeploy API proxies to your cluster
• Get the deployment status of pods in your cluster

To access the hybrid UI and add an environment:

1. Open theApigee UI.

   If this is the first time you are logging in, hybrid displays a consent dialog box:

   

2. If you are prompted to select from more than one account, choose the account that owns the project you created inStep 2: Create a Google Cloud project.
3. ClickAllow.

   Your browser navigates to the hybrid UI main landing page:

   

4. Ensure that your hybrid-enabled organization is selected from the organization drop-down list. If not, select it from the drop-down list, as the following example shows:

   

   Note that when you select a hybrid-enabled organization from the drop-down list, the hybrid UI displays the Apigee organization name and the GCP project name in the header. In many cases, the Apigee organization name and GCP project name are the same.

5. ClickAdmin > Environments > Overview.

   TheEnvironments view is displayed, with no environments (yet):

   

6. Click+Environment in the upper right corner of the UI.

   TheDefine a new environment dialog box is displayed:

   

7. Enter the following information in theNew Environment dialog box:
   1. Display name: A friendly name for the environment that is used in the UI. For example, "My First Environment" or "test". Unlike, theEnvironment name, theDiplay name can include upper case and other special characters. Required.
   2. Environment name: The programmatic name for the environment; also known as theenvironment ID. Required.

      For example, "my-environment" or "test".

      An environment name can contain only lower-case letters, numbers, and hyphens. You cannot use upper-case letters or any other special characters. In addition, theEnvironment name can be up to a maximum of 32 characters long. For example:my-test-env ormy-test-env-42.

      You will also use this name in theoverrides.yaml file when youinstall the hybrid runtime.

      TheDisplay name and theEnvironment name can be different.

   3. Description: Additional information about the environment that you want to add as a reminder of the purpose of the environment. For example, "Created during initial installation". Optional.
8. ClickCreate.

   Apigee creates the new environment and indicates that it is "Pending Provisioning":

   

   In a few moments, it will be "provisioned":

   

   However, you’re not quite done. You also need to add your new environment to the runtime’s overrides.yaml file—but first you've got to install the runtime, so let's not get ahead of ourselves.

Congratulations!

Now that you've created a GCP account and project, gotten an org provisioned, had a snack, added some service accounts and other users, and created a new environment, you're ready to install the hybrid runtime on your Kubernetes cluster.

Next step

To continue with the installation, seeRuntime installation: Before you begin.