After adding a Service to your Application, define Environment to deploy your Service. Environment represents your deployment infrastructures, such as Dev, QA, Stage, Production, etc.
In this topic:
- Before You Begin
- Step 1: Add an Environment
- Step 2: Add Infrastructure Definition
- Step 3: Override a Service Configuration
- Step 4: Add Service Verification
- Next Steps
Before You Begin
Step 1: Add an Environment
To add an environment, do the following:
- Click Setup.
- Click an Application.
- Click Environments.
- Click Add Environment. The Environment dialog appears.
- Enter a name and description for the Environment. For example, the name DEV with the description: This is the development environment for example.com.
- In Environment Type, choose Production or Non-Production.
- Click Submit. The Environment Overview appears. Here you can add the Service Infrastructure and overrides to the configurations of the Services that use this Environment.
Step 2: Add Infrastructure Definition
The Infrastructure Definition is where you specify the target infrastructure for your deployment. The target infrastructure can be an existing infrastructure or an infrastructure provisioner, such as Terraform or CloudFormation. For detailed information on adding Infrastructure Definition, see Add an Infrastructure Definition.
Step 3: Override a Service Configuration
You can configure your Environment to override settings of the Services that use the Environment. For example, a Service might use a specific values.yaml file, but your Environment might need to change the name and namespace of the Deployment object because it is deploying the Service to a QA Environment.
To override a Service configuration, do the following:
- In an Application, open an Environment.
- Click Add Configuration Overrides. The Service Configuration Override dialog appears.
- In Service, click the name of the Service you want to override. Depending on the type of Service you select, the Override Type options will be different. Here is an example of the options available when a Service with Kubernetes type is used.
- Click an Override Type option.
- Enter the override and click SUBMIT.
Step 4: Add Service Verification
24/7 Service Guard applies Harness Continuous Verification unsupervised machine-learning to detect regressions and anomalies across transactions and events for the service and displays the results in the 24/7 Service Guard dashboard. For detailed information on adding Service Verification, see Set Up Service Guard.