Concourse is a continuous integration tool that lets you build, scale, and monitor pipelines outside of your Tanzu Operations Manager deployment. Using Concourse, you can set up production pipelines to deploy and manage your apps in real time. Concourse for VMware Tanzu is an officially supported, long-term-stable version distributed through the Broadcom Support portal.
For more information, see What is Concourse for VMware Tanzu?
Concourse Architecture
Concourse is composed of two major sub-components: the web service (ATC and TSA) and workers.
For information about the architecture of Concourse and its components, see Concourse Architecture.
For more information about the open source Concourse project that powers Concourse for VMware Tanzu, see the Concourse documentation.
Concourse Compatibility
See the following tables for BOSH, Helm, and PostgreSQL release compatibility with Concourse.
BOSH Concourse Compatibility
The values in the “Tested” columns indicate that Concourse was tested with the listed Stemcell or product version upon release. This does not mean that Concourse is restricted to those dependencies.
| Concourse Version | PostgreSQL | Tested Stemcell | Supported Stemcells | Tested CredHub |
|---|---|---|---|---|
| v7.11.2+LTS-T | 11+ External | Jammy 1.351 | 1.x | 2.12.60 |
| v7.9.1+LTS-T | 11+ External | Jammy 1.80 | 1.x | 2.12.18 |
| v7.4.0 | 9.6+ External | Xenial 621.183 | 621.x | 2.9.0 |
Helm Concourse Compatibility
Concourse is compatible with CredHub versions 2.1.2 and later. It is not compatible with versions 2.0.0 to 2.1.1.
| Concourse Version | PostgreSQL | Tested K8s | Tested Helm | Tested Kubectl |
|---|---|---|---|---|
| v7.11.2+LTS-T | 11+ External | GKE v1.26.12 | 3.14.0 | 1.29.2 |
| v7.9.1+LTS-T | 11+ External | TKGi 1.14 | 3.11.0 | 1.23.14 |
| v7.4.0 | 9.6+ External | TKGi 1.12.0 | 3.7.1 | 1.21.5 |
If you are using PostgreSQL v11.1 or v11.2, set max_parallel_workers_per_gather to 0. This corrects a PostgreSQL infinite parallel query issue.
For more information, see max_parallel_workers_per_gather (integer) and BUG #15585: infinite DynamicSharedMemoryControlLock waiting in parallel query in the PostgreSQL documentation.
PostgreSQL and Concourse
Concourse v7.11.2+LTS-T was tested on PostgreSQL v15. For more information, see:
Installing Concourse for VMware Tanzu
Concourse for VMware Tanzu is distributed as both a BOSH release and a Helm Chart.
- The BOSH release requires the operator to install and maintain an independent BOSH Director.
- While the BOSH release targets a BOSH director and deploys to virtual machines (VMs), the Helm Chart release targets Kubernetes clusters using the templating and release management of Helm.
When you are ready to get started with either release, see the step-by-step guide, Installing Concourse for VMware Tanzu.
To troubleshoot your Concourse for VMware Tanzu installation, see Troubleshooting.
Enterprise Security Considerations
In addition to installation and operation, it’s important to control information and system security.
| Database Encryption | Concourse lets you encrypt sensitive information before it reaches the database. By using encryption, you ensure that plaintext credentials do not exist in memory for longer than absolutely necessary. For more information, see Encrypting Concourse Databases |
|---|---|
| Credential Management | With Concourse credential management, pipeline credentials can be parameterized with
((parameters))
in your pipeline or task config files. Credential management also allows for credentials to be rotated and managed from outside the pipeline or team, and prevents them from being revealed by get-pipeline. For more information, see Credential Management in Concourse. |
| Team Authentication | Concourse provides options for team authorization to protect confidential or sensitive data. For more information, see Configuring Team Authentication. |
Monitoring and Troubleshooting
Concourse can emit metrics about both the system health itself and about the builds that it is running. Operators can tap into these metrics to observe the health of the system.
For more information, see Monitoring and Troubleshooting.
Content feedback and comments