Prerequisites and Background Information
Before you install Concourse for VMware Tanzu, you must have the following:
- A supported IaaS provider: AWS, Azure, GCP, or vSphere
Deploying with BOSH
- 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 Ops Manager deployment. This is because Concourse for VMware Tanzu 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 this from VMware Tanzu Network.
The stemcell for your IaaS. You'll need these when you create your Concourse deployment manifest.
Concourse v6.7.3 was tested on Stemcell 621.92 (Xenial) upon release and supports the 621.* Stemcell family.
To download an Ubuntu Xenial stemcell from VMware Tanzu Network, see Stemcells for PCF (Ubuntu Xenial).
Deploying on Kubernetes with Helm
The VMware Concourse team has tested deploying with Helm using the following prerequisites:
- Kubernetes cluster (1.11+)
- VMware recommends VMware Tanzu Kubernetes Grid Integrated Edition (TKGi)
- This process has been tested with TKGi 1.7
- TKGi must have support for privileged containers activated. See enabling privileged containers on TKGi for more information
- kubectl v1.15
- For help, read the Install and Set Up kubectl guide.
- Concourse Helm Chart. Download this from VMware Tanzu Network.
- Private container registry (optional)
- VMware recommends Harbor
- Docker CLI
- Helm CLI
Enabling privileged containers on TKGi
To enable the ability to have privileged containers on TKGi, the plan configured to be used in the cluster must be changed.
Head to the plan configuration in OpsManager, and mark the
Allow Privileged checkbox near the end:
1 2 3 4 5
Concourse v6.7.3 was tested on PostgreSQL v12.3. For more information, see VMware 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.