Deprecated - used Control Tower instead
Bug fix: Extension of the InfluxDB retention policy period (now 28 days) to prevent web nodes running out of disk space.
Deploys:
AWS
GCP
Note to build locally you will need to clone concourse-up-ops (version 0.0.181) to the same level as concourse-up to get the required manifests and ops files.
Redeployments were failing after AWS' RDS upgrade beyond v9.6.6. This patch release fixes this bug.
Deploys:
AWS
GCP
Note to build locally you will need to clone concourse-up-ops (version 0.0.174) to the same level as concourse-up to get the required manifests and ops files.
This release adds the custom networking feature, allowing the user to specify the CIDR ranges that should be used for the subnets that Concourse-Up creates. This introduces 5 new flags including --vpc-network-range.
It also introduces more effective configuration management, fixing an issue that prevented failed deployments from being resumed, if they failed early.
Deploys:
AWS
GCP
Note to build locally you will need to clone concourse-up-ops (version 0.0.158) to the same level as concourse-up to get the required manifests and ops files.
Yesterday a new major version of the GCP terraform provider was released. It contains various breaking changes. One of these prevents Concourse-Up from deploying properly to GCP. Previously we were not pinning terraform provider versions so all previous Concourse-Up versions will no longer work when deploying to GCP. This release pins to 1.X versions of the provider.
Deploys:
AWS
Note to build locally you will need to clone concourse-up-ops (version 0.0.148) to the same level as concourse-up to get the required manifests and ops files.
This release supports --iaas gcp for choosing GCP as the target IaaS. Please see the Concourse-Up README for details.
Deploys:
AWS
Note to build locally you will need to clone concourse-up-ops (version 0.0.141) to the same level as concourse-up to get the required manifests and ops files.
renew-https-cert job triggered immediately, causing a redeploy minutes after initial deployment.Deploys:
AWS
Note to build locally you will need to clone concourse-up-ops (version 0.0.141) to the same level as concourse-up to get the required manifests and ops files.
Deploys:
AWS
Note to build locally you will need to clone concourse-up-ops (version 0.0.136) to the same level as concourse-up to get the required manifests and ops files.
As a follow up to the NATS certificate expiry issue mentioned in v0.17.0 we have implemented a mechanism to renew this cert using concourse-up
There is now a maintain command. You can rotate your NATS certificates using
concourse-up maintain --renew-nats-cert
You can read more details in the docs
Please Note: this command involves recreating both the director and all the Concourse vms several times which will cause downtime
Deploys:
Note to build locally you will need to clone concourse-up-ops (version 9c02a5e2d2df804f60da2f4da063962d578a37e7) to the same level as concourse-up to get the required manifests and ops files.
The CA certificates for NATS in BOSH directors are hard coded to expire after one year. Once this cert expires its challenging to fix.
In order to offer more visibility into this we have implemented a new flag on info to show the expiration date of your director's cert.
$ concourse-up info a-deployment --cert-expiry
Jan 12 13:04:55 2020 GMT
This information will also appear in the standard info output.
If your deployment is getting close to expiry you can follow the BOSH docs on renewing certs.
Deploys:
Note to build locally you will need to clone concourse-up-ops (version 0.0.103) to the same level as concourse-up to get the required manifests and ops files.
This release fixes two bugs.
#78 - Previously when deploying with the --allow-ips flag credhub would not function since it needs the ATC's public IP to be whitelisted on the security group for port 8844. Thanks to @steveYeah for raising this!
#79 - A while ago we implemented a pre-condition check on concourse-up info to make sure the user's IP is whitelisted on the director security group. This was to avoid unnecessary waiting and ambiguous errors. Unfortunately our implementation was naive and only supported the IP being inputted in the security group as a /32. We now check that the appropriate rules exist for a CIDR block that contains the user's IP. Thanks to @sneakybeaky for raising this!
Deploys:
Note to build locally you will need to clone concourse-up-ops (version 0.0.102) to the same level as concourse-up to get the required manifests and ops files.