At this point, you have done the following:
- Created a space
- Connected an asset repository and autogenerated blueprints out of some assets
- Created an execution host that will handle the deployment and teardown of the environments in the Kubernetes cluster
You are now ready to launch your first environment.
- Open your space.
- In the Blueprints page, Publish a suitable autogenerated blueprint.
- Launch the blueprint.
- Provide the name of the Kubernetes cluster namespace and execution host to use. Later on, you will want to add these details to the autogenerated blueprint, as explained in Customizing Autogenerated Blueprints.
- Wait until the environment is active and use as needed. URLs to the environment's applications are typically provided as outputs - these can be found in the environment's Quicklinks on the right, or in the Parameters pane.
- Check out the Resources pane to get details about your environment's resources. Use this tab to understand what assets each grain spun up, get connection details to specific resources, and more.
If someone makes changes to the blueprint's asset or the environment's cloud resources while the environment is running, you will see an Updates Available link in the environment page. Click it to view and resolve the changes. It has two sections:
Updates shows changes made to the asset's definition file, allowing you to optionally update the environment
Drift Detection shows any of the environment's resources that were modified externally. Click the error to see the modifications, and Reconcile to revert a resource back to its original state.