Environments
Network isolation is configured on a per-namespace basis, and you can manage the following settings within the environment.
An environment corresponds to a namespace in a Kubernetes cluster.
Learn more about ale’s work unit hierarchy, from spaces to services, in the following section.
Create a New Environment
When creating a project, an environment named
mainis created simultaneously.
Environments can only be created as part of a project.
Environment Details
The header shows the parent project name of the current environment, with a selector in the top-right corner to switch environments. In the Information tab below, you can view details of services within the selected environment and manage the services directly.
Add Environments
Add as Empty Environment
Navigate to the environment selector (top right) and click “Create New Environment”. Choose “Create as Empty Environment”, configure your environment name and select a cluster, then click
Createto complete the process.
Add by Cloning
To clone an environment, select an environment with services as a source environment. The new environment will be created with all services cloned from the source environment.
Clone your source environment to easily create development, production, or QA environments. Newly cloned services are in a stopped state and can be launched all at once by clicking Start All in the evnironment selector.
When migrating an environment, secrets from the source environment are not copied over. See the Secret Management page to configure secrets for your new environment.
Management
Switch Environments
To switch between environments, click the environment selector in the top right corner.
Each environment (except for main) is assigned a distinct color indicator. These color codes help you quickly identify which environment you’re working with when deploying or modifying services.
Deploy with YAML File
You can download YAML configuration files containing all service deployment settings from your environment and apply them to a new environment using drag & drop.
YAML deployment scripts simplify cloning environments. For more information, See the Environment Migration page.
Set as Default Environment
To set a default environment, click
Set as Default Environmentin the environment information section of the Settings tab. Since the default environment is automatically loaded when you select a project, it’s recommended to set your most frequently used environment as default.
Delete Environment
Click
Delete a environmentat the bottom of the Settings tab.
If only one environment exists in the project, the button will show as Delete a project, and both the project and environment will be deleted.
Secret Management
In the secret management section of the Settings tab, click the icon on the right to store common variables and secrets that can be used by services in the environment.
You can quickly configure secrets using drag & drop. For more details, see the Environment Variable Management page.
Secrets can be stored and shared at the environment level.
Firewall Settings
You can enable external TCP connections from other environments, projects, and external services via the firewall management section in the Settings tab. When enabled, this allows access from all IP addresses - configure with caution.
For more details on communication with other services, see the Service Connections page.