1588769 - decommission AWS workers once we're fully migrated to GCP

Status: RESOLVED FIXED

(Release Engineering :: General, task)

Description

[Mihai Tabara [:mtabara]⌚️GMT]

We're slowly getting to the point where we can start decommisioning old puppet AWS infrastructure.

Namely:

• beetmover, bouncer and shipit workers are already used in 70 cycle, mozilla-release. We should uplift these to esr68 as well. Once ESR60 is EOL (22th October) and ESR68 is up-to-date with these workers, we can stop (and decommission days/weeks later) AWS workers
• addon, balrog, signing and pushsnap are in beta cycle 71. Once they reach release in 6 weeks time, we can retire those workers too.
• pushapk and treescript are WIP to be migrated to beta this week so likely they will fall in the same category as above

Comment 1

[Aki Sasaki (not active)]

I think this bug had to do with scriptworker-k8s, which has all been off AWS for a while now.