dev, staging, production).They allow you to test, deploy, and manage applications separately.
Rename an Environment
You can rename an environment to better reflect its purpose.- Navigate to Environment → Settings.
- Update the Environment Name field.
- Click Save.
⚠️ Renaming does not affect workloads, secrets, or configurations linked to the environment.
Clone an Environment
Easily duplicate an existing environment to create a copy with the same configurations.- Go to Environment → Settings.
- Select Clone Environment.
- Provide a new name for the cloned environment.
- Click Clone.
- Workloads and configurations
- Secrets and variables
- Networking settings
⚠️ Billing and usage are tracked separately for cloned environments.
Delete an Environment
Environments can be permanently deleted when no longer needed.- Navigate to Environment → Settings.
- Scroll to Delete Environment.
- Confirm by clicking Delete.
⚠️ This action is irreversible. All workloads, secrets, and associated billing data will be removed.
Best Practices
- Use cloning to quickly set up staging from production.
- Keep environment names descriptive (
dev2,staging,prod). - Always review secrets before cloning to avoid leaking sensitive data.
- Delete unused environments to optimize costs.