Concourse-Up becomes Control Tower

Mar 25, 2019| Eva Dinckel and Dan Young

What happened?

Concourse-Up has changed its name to Control Tower for Concourse. The repo and release naming has changed, along with all mention of concourse-up in the codebase, and the resources that Control Tower creates. In all other ways, Control Tower is the same thing as Concouse-Up.

Why have we done this?

The main reason for doing this is the Concourse CI trademark guidelines. By meeting these guidelines, we now have more freedom over the direction we can take Control Tower as a product, including how we distribute or commercialise it in the future.

What else is new?

As well as containing a collection of bug fixes and improvements, Control Tower also supports the long awaited Concourse 5.0, which introduces a number of improvements and the first steps towards Role Base Access Control (RBAC).

Control Tower supports deployments on GCP as well as AWS. As part of our new IaaS-provider agnostic direction, we now require users to provide the --iaas flag when deploying.

How do I upgrade to Control Tower?

We are currently looking at ways to provide a smooth, automated process to migrate your Concourse-Up deployment to a Control Tower deployment. If this is very important to you, please let us know your thoughts. In the meantime, Colin Simmons from our team has written a post describing how we migrated our own deployment.

What’s next?

We’re still committed to providing support for Azure users, so stay tuned for that. We’re also working on providing Control Tower via channels other than Github, to reach a wider set of users and would be interested to get your feedback on issues such as commercial support or other useful enterprise features.

To chat with our team and other users about Control Tower, please join our community on Slack Concourse-Up User Slack and share your thoughts!