Installing starter deployments

A deployment that is intended for demonstration purposes is much quicker to install than a production deployment. Unix-based shell scripts are provided to help a cluster administrator set up the cluster and for a non-administrator user to run the installation. The Cloud Pak capabilities to install are packaged into several patterns to simplify integration and share resources.

Before you begin

Restriction: Air gap environments are not supported for starter deployments. Only one starter deployment is allowed per cluster.

For more information about starter deployments and how to plan for them, see Planning for a starter installation. The following diagram shows the steps that are involved in installing a starter deployment.

Installation workflow for evaluation purposes

The starter deployment type is intended for evaluation purposes. It uses some utility images such as openldap, busybox, and alpine to deploy a complete CP4BACluster instance with some default services. These images are not suitable for production. The starter type also sets default credentials to make it easy to deploy, and for this reason you must not keep a starter deployment for development or for production.

Deployments for development and for production must use a production deployment.