Step 3. Define a Deployment YAML Specification

Define a legacy deployment in a YAML specification file. Each file can define a single deployment. The file can optionally define a Kubernetes Horizontal Pod Autoscaler, service, or Ingress associated with the deployment.

Important: The YAML specification file must use the Kubernetes API version apps/v1 to define each deployment.

The YAML specification file can contain the following components:

Deployment
Use for a legacy deployment of one or more execution Data Collectors that can be manually scaled. To manually scale a deployment, you modify a deployment in the Control Hub UI to increase the number of Data Collector instances.
For a sample specification file, see Deployment Sample.
Deployment associated with a Kubernetes Horizontal Pod Autoscaler
Use for a legacy deployment of one or more execution Data Collectors that must automatically scale during times of peak performance. Define the deployment and Horizontal Pod Autoscaler in the same YAML specification file. The Kubernetes Horizontal Pod Autoscaler automatically scales the deployment based on CPU utilization. For more information, see the Kubernetes Horizontal Pod Autoscaler documentation.
For a sample specification file, see Deployment and Horizontal Pod Autoscaler Sample.
Deployment associated with a Kubernetes service and Ingress
Use for a legacy deployment of a single authoring Data Collector. To allow users to log into a Data Collector container automatically provisioned on the Kubernetes cluster, you must expose the Data Collector container outside the cluster using a Kubernetes service.
You can also optionally associate an Ingress with the service. An Ingress can provide load balancing, SSL termination, and name-based virtual hosting to the services in a Kubernetes cluster.
Define the deployment, service, and Ingress in the same YAML specification file. For more information, see the Kubernetes services and Ingress documentation.
For a sample specification file, see Deployment, Service, and Ingress Sample.
When provisioning Data Collectors to AWS Fargate with Amazon Elastic Kubernetes Service (EKS), you must add additional attributes to the deployment YAML specification file.
Important: For a deployment to be manually or automatically scaled, jobs that run on Data Collector containers in that deployment must be configured to automatically scale out pipeline processing.