control-tower
control-tower copied to clipboard
Changing domain leaves old certificate on credhub
I am working on migrating from concourse-up to control tower and a I want to do the following.
- Leave my concourse-up deployment deployed at myconcourse.example.com
- Deploy a new concourse using control-tower at myconcourse-v2.example.com
- Migrate pipelines across one by one
- Leave both running a while just to access logs and history
- Delete the concourse-up deployment
- Change the domain for the control-tower deployment to myconcourse.example.com
I think that there is a problem with set 6. I have experimented deploying with control-tower to a domain for example: mytest-v2.example.com and then changing the domain in the deploy script to mytest.example.com and running again.
This successfully runs and changes the domains but the certificate used by credhub is the old one. So I get errors like this in my resources:
Finding variable 'ssh-private-key': Get https://mytest.example.com:8844/info: x509: certificate is valid for mytest-v2.example.com, not mytest.example.com
Thanks for making us aware of this @kurtmc - we'll take a look and update the guide as appropriate, to give guidance on certs.