Archive Gemnasium client/server architecture
TODO: add technical details for this issue after completing discovery in https://gitlab.com/gitlab-org/gitlab-ee/issues/12930 It's been decided to not wait for possible reuse in future feature.
release notes not needed
It's been more than a year that we updated the gemnasium analyzer to not use the advisory DB from this architecture (
12.5
). Back at that time we we're worried to have customers using older images and not updating them which would be broken if we decomissioned this infra. Though, I think it's really unlikely to be the case today.
So the only remaining usage of this architecture is the web interface at https://deps.sec.gitlab.com and I don't think this was ever advertised. To me this seems to be the only reason to advertise the change.
Implementation plan
- Verify activity (inbound traffic to the WEB/API endpoints)
- Do a backup/archive of the whole PGSQL DB for the purpose of restoration if there is some immediate problem that arises after the decom. Delete the backup after 30 days to ensure no conflict with our privacy policy.
- Delete the whole cluster (no need to remove resources one by one)
- Delete deps.sec.gitlab.com from the DNS
- Archive https://gitlab.com/gitlab-org/security-products/gemnasium/gcp-config.