Engine Labels

A deployment defines the engine labels to assign to all engine instances managed by the deployment. Engine labels determine the group of engine instances that can run a job.

By default when you create a deployment, Control Hub assigns an engine label to the deployment using the same name as the deployment. All engine instances managed by the deployment inherit the label.

When you use the default engine label created for a deployment and inherited by all engine instances, you ensure that all engine instances that can run a job have an identical configuration. When you create a job, you can simply select the deployment that you want to use to run the job. Control Hub then automatically assigns the engine label defined for the deployment to the job. When you start the job, Control Hub runs a pipeline instance on an available engine instance managed by the deployment.

For example, you create a deployment named Marketing. Control Hub creates and assigns a Marketing engine label to the deployment. All engine instances managed by the deployment inherit the Marketing engine label. When you create a job, you select the Marketing deployment which assigns the Marketing engine label to the job. When you start the job, the job can only run on engine instances managed by the Marketing deployment.