Can we make use of canary.gitlab.com or tear it down?
As the title says, canary is a part of our release deployments but it is not being used at all. For that reason, I wonder why are we even deploying there if we are not getting any benefit from it.
Cons for keeping it
Canary is not useful when the release has migrations because it does not have write access to the database.
Most of our migrations are concentrated in first couple of RCs, for sure in the first RC that lands in production.
Pros for keeping it
For most others, canary would be absolutely useful.
For example, we (as a company) could have easily caught https://gitlab.com/gitlab-org/gitlab-ee/issues/4911 if the company was using the canary. We would have possibly been able to catch the SSH issue because one of our devs has reported it in Slack
I think the pros outweigh the cons. If we don't want to force everyone to use canary, lets shut down this environment or remove it from the release process.