Your account can be associated with multiple environments considering the following restrictions:
- Only account administrators can create or delete environments.
- An environment quota is limited by the account available quota.
For more information, check common use cases for environments.
Obtain a list of all your available environments executing:
playground env list
Current environment: account1/env1 CURRENT ACCOUNT NAME ID DESCRIPTION * account1 env1 <env1_id> description environment 1 account1 env2 <env2_id> description environment 2 account2 env3 <env3_id> description environment 3
or list only the environments of one account:
playground env list account1
Current environment: account1/env1 CURRENT ACCOUNT NAME ID DESCRIPTION * account1 env1 <env1_id> description environment 1 account1 env2 <env2_id> description environment 2
Get the environment detailed information executing:
playground env info <account>/<environment>
Server version: v1.20.9-gke.1001 OAM: v0.2.1 CREATION_TIME CREATED_BY 2021-09-01 16:03:48.452752 +0000 UTC <username> ACCOUNT ENV CPU RAM STORAGE <account> <environment> 0/1 0/4000 0/1000 DESCRIPTION environment description
As administrator of an account, you can create new environments in the account.
playground env create <account_name>/<env_name> \ --description=”This is a test” --cpu=1 --ram=2G --storage=5G --set-as-default=true
Flags: --cpu float32 Cpu quota --description string Environment description --ram string Ram quota --set-as-default Set environment as default --storage string Storage quota
If the quota is not indicated (cpu, ram and/or storage), the environment will be created with the default quota associated with your subscription plan. You may create many environments to accommodate your specific use case, but the number of maximum environments is limited by the subscription plan. If you need more environments, consider upgrading your subscription plan, or contact us for special requests.
If the environments that is created requires more quota than available, the following error will be shown:
rpc error: code = Internal desc = Error creating environment. Not enough resources available
An application can be deployed in any of the environments you have access even if those belong to multiple accounts. When the login operation is performed, your credentials will allow you access to your default environment. To work in another environment, you will need to either use the
--env argument when supported, or change manually to another environment with the use command.
playground env use <account1>/<env2>
Logged into account [account1] - environment [env2]
To check which is the environment currently in use in the given session, execute a list operation and check for which environment is marked in use.
playground env list
Current environment: account1/env1 CURRENT ACCOUNT NAME ID DESCRIPTION <account1> <env1> <env1_id> <description environment 1> * <account1> <env2 > <env2_id> <description environment 2> <account2> <env3> <env3_id> <description environment 3>