You can manage your environments with a combination of the Google Cloud console and the hybrid
runtime configuration file. This section describes how to create a new environment, edit an
environment's details, and delete an existing environment with the Google Cloud. You must then update
your overrides.yaml on the runtime plane to complete the creation or deletion of an environment.
Create a new environment in the UI
To create a new environment, you must do the following (in this order):
Create a new environment in the Google Cloud console.
AND
Provision the new environment in your overrides file.
You can create up to 75 environments per organization.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eThis documentation is for Apigee hybrid version 1.1, which is end-of-life, and users should upgrade to a newer version.\u003c/p\u003e\n"],["\u003cp\u003eManaging environments involves using both the Google Cloud console and the hybrid runtime configuration file, with actions in the UI requiring subsequent updates to the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file on the runtime plane.\u003c/p\u003e\n"],["\u003cp\u003eCreating a new environment requires first creating it in the Google Cloud console and then provisioning it in the runtime's \u003ccode\u003eoverrides\u003c/code\u003e file, with a potential delay before provisioning.\u003c/p\u003e\n"],["\u003cp\u003eEditing an environment in the UI allows changes to the display name and description, and deleting environments requires actions in both the UI and the runtime's \u003ccode\u003eoverrides.yaml\u003c/code\u003e file.\u003c/p\u003e\n"],["\u003cp\u003eA maximum of 75 environments can be created per organization.\u003c/p\u003e\n"]]],[],null,["# Manage environments\n\n| 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, see [Supported versions](/apigee/docs/hybrid/supported-platforms#supported-versions).\n| **More Information** \n|\n| For more information, see:\n|\n| - [About environments and environment groups](/apigee/docs/api-platform/fundamentals/environments-overview)\n\nYou can manage your environments with a combination of the [Google Cloud console](https://console.cloud.google.com) and the hybrid\nruntime configuration file. This section describes how to create a new environment, edit an\nenvironment's details, and delete an existing environment with the Google Cloud. You must then update\nyour overrides.yaml on the runtime plane to complete the creation or deletion of an environment.\n| **Note:** Do not create any new environments until you have installed the hybrid runtime on your cluster as described in [Part 2: Runtime quickstart](/apigee/docs/hybrid/v1.1/install-before-begin).\n\nCreate a new environment in the UI\n----------------------------------\n\nTo create a new environment, you must do the following (in this order):\n\n1. Create a new environment in the Google Cloud console. **AND**\n\n2. Provision the new environment in your overrides file.\n\n| **Note:** After you create a new environment in the UI, there can be a several minute delay before you can provision it in the runtime.\n\nYou can create up to 75 environments per organization.\n\n**To create a new environment:**\n\n1. Create the new environment as described in [Creating\n environments](/apigee/docs/api-platform/fundamentals/environments-working-with#create).\n\n There can be a several minute delay before the new environment is provisioned.\n\n Even when provisioning is done, you have one more step to perform. You must still add the\n environment to the runtime's overrides.yaml file.\n2. On the Kubernetes administration machine, add the new environment to the runtime's overrides file, as described in [How to add multiple environments](/apigee/docs/hybrid/v1.1/environment-create#how-to-add-multiple-environments).\n\nEdit an existing environment in the UI\n--------------------------------------\n\nYou can change the following properties of an existing environment in the UI:\n\n- Display name\n- Description\n\nTo edit an existing environment, see\n[Editing environments](/apigee/docs/api-platform/fundamentals/environments-working-with#edit).\n\nDelete an existing environment\n------------------------------\n\nTo delete an existing environment, you must do the following (in this order):\n\n1. Delete the environment in the UI, as described in this section **AND**\n\n2. Delete the environment from the runtime, as described in [Delete environments](/apigee/docs/hybrid/v1.1/environment-delete).\n\n**To delete an existing environment:**\n\n1. Delete the environment in the Apigee UI using the instructions in [Deleting environments](/apigee/docs/api-platform/fundamentals/environments-working-with#delete).\n\n The environment's card in the UI displays a \"Pending Deletion\" label while Apigee deletes the\n environment.\n\n There can be a several minute delay before the deletion is completed.\n | **Note:** You're not quite done. You must still delete the environment from the runtime's `overrides.yaml` file.\n2. Delete the environment from the runtime's `overrides.yaml` file, as described in [Delete environments](/apigee/docs/hybrid/v1.1/environment-delete)."]]