Step 5: Add a new environment in the hybrid UI

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

Apigee recommends that you create no more than 20 environments.

The hybrid UI includes most of Apigee Edge UI’s functionality, plus some hybrid-specific 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 the Apigee hybrid UI.

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

    A dialog that asks the user
    to give services access

  2. If you are prompted to select from more than one account, choose the account that owns the project you created in Step 2: Create a GCP project.
  3. Click Allow.

    Your browser navigates to the hybrid UI main landing page:

    The landing page in the Apigee
    hybrid UI, which consists of left-hand navigation and large links/images

    The hybrid UI is similar to the Edge UI. Developer tasks, such as creating and editing API proxies, controlling proxies with flows, and handling faults, are very similar. Some administrative and operational tasks, however, such as managing users and deploying API proxies, are very different from the Edge UI. The topics in Administer describe the processes that are different.

  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:

    A list of organizations that are hybrid enabled

    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. Click Admin > Environments > Overview.

    The Environments view is displayed, with no environments (yet):

    The Environments view, which is blank (no environments)

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

    The Define a new environment dialog box is displayed:

    The Define a new environment dialog box

  7. Enter the following information in the New 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, the Environment name, the Diplay name can include upper case and other special characters. Required.
    2. Environment name: The programmatic name for the environment; also known as the environment ID. Required.

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

      You will also use this name in the overrides.yaml file when you install the hybrid runtime.

      The Display name and the Environment 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. Click Create.

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

    Badge showing the 'Pending Provisioning'
    message

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

    Badge showing that the new
    environment was 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.

Next step

To continue with the installation, see Runtime installation: Before you begin.