Multi-Environment

This documentation will introduce how to use env-binding to automate multi-stage application rollout across multiple environments.

Users usually have two or more environments to deploy applications to. For example, dev environment to test the application code, and production environment to deploy applications to serve live traffic. For different environments, the deployment configuration also has some nuance.

We apply the Application in the example.

After the Application is created, a configured Application will be created under the demo namespace.

If you want to learn more about env-binding, please refer to Multi Cluster Deployment.

env

Name	Desc	Type	Required	Default Value
name	environment name	string	true	null
patch	configure the components of the Application	`patch`	false	null
placement	resource scheduling strategy, choose to deploy the configured resources to the specified cluster or namespace		true	null
selector	identify which components to be deployed for this environment, default to be empty which means deploying all components	`selector`	false	null

placement

Name	Desc	Type	Required	Default Value
clusterSelector	select deploy cluster by cluster name	`clusterSelector`	false	null
namespaceSelector	select deploy namespace by namespace name	`namespaceSelector`	false	null

selector

clusterSelector

Name	Desc	Type	Required	Default Value
name	cluster name	string	false	null

You need to upgrade to KubeVela v1.1.5+ to enable namespaceSelector.