- Deployments Overview
A deployment is a group of identical engine instances deployed within an environment. A deployment defines the IBM StreamSets engine type, version, and configuration to use. You can deploy and launch multiple instances of the configured engine.
- Stage Libraries
A deployment defines the stage libraries that are installed on the engine. The installed stage libraries determine the stages that you can use when designing pipelines and the credential stores that pipelines can retrieve secrets from.
- Engine Advanced Configuration
A deployment defines the advanced configuration properties for the engine. As you get started with IBM StreamSets, the default values should work in most cases.
- External Resources
IBM StreamSets engines can require access to external files and libraries, depending on how you design pipelines.
- 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.
- Resource Thresholds
- Init Script
When you configure a cloud service provider deployment, you can define an initialization script that Control Hub runs on each newly provisioned instance in your cloud account. The script runs in parallel to the provisioning process.
- Self-Managed Deployments
You can create a self-managed deployment for an active self-managed environment.
- Amazon EC2 Deployments
- Azure VM Deployments
- GCE Deployments
- Kubernetes Deployments
You can create a Control Hub Kubernetes deployment for an active Kubernetes environment.
- Deployment Tags
A deployment tag identifies similar deployments. Use tags to easily search and filter deployments when viewing them in the Deployments view. For example, you might want to group deployments by the engine type or project.
- Managing Deployments
- Monitoring Deployments
- Upgrading Engines
- User-Provided Stage Library Mode
- Troubleshooting