Before you install Pivotal Concourse, you must have the following:
- A supported IaaS provider: AWS, Azure, GCP, or vSphere
- A BOSH Director. For more information about the BOSH Director, see Deploying BOSH with create-env in the BOSH documentation.
It is not recommended to use a BOSH Director associated with an existing PCF deployment. This is because Pivotal Concourse can conflict with other tiles deploying on Ops Manager at the same time.
- BOSH CLI v5.x. For more information, see Installing the CLI in the BOSH documentation.
- Concourse BOSH release. Download these from Pivotal Network.
- The stemcell for your IaaS. You'll need these when you create your Concourse deployment manifest. Concourse v4.2.4 was tested on Stemcell 250.38 (Xenial) upon release and supports the 250.* Stemcell family. To download an Ubuntu Xenial stemcell from Pivotal Network, see Stemcells for PCF (Ubuntu Xenial).
Concourse v4.2.4 was tested on PostgreSQL v9.5. For more information, see Pivotal Postgres.
Past versions of Concourse BOSH release shipped with their own internal PostgreSQL. As of Concourse v3.6.0, and with all future versions, the Concourse BOSH release no longer supplies an internal PostgreSQL.
Learn About Deploying Concourse with PostgresDB
Concourse v3.6.0 and later no longer manage an internal Postgres database with the BOSH release. An operator needs to instruct Concourse to connect to one of the following:
- An externally-managed Postgres database.
- A BOSH-managed Cloud Foundry Postgres release. For more information, see postgres/38 in the BOSH documentation.
You need to configure the
postgresql properties of the ATC job for your database.
For a list of these properties, see postgresql in the BOSH documentation.