Shut down GCP Cluster: gl-remote-dev-stg-0c1d2143

Overview

The legacy cluster gl-remote-dev-stg-0c1d2143 is planned to be shut down by 20th of December due to cost and operational maintenance burdens.

This's a long overdue cleanup since the dissolution of engineering productivity team.

This cluster has been configured for internal use only.

Impacted users and groups

Per usage, there're 40 GitLab team members who are running their workspaces on this cluster, 34 active workspaces in 10 months as the highest record.

Alternative solutions

GitLab team members are advised to pursue the alternatives suggested here by Runners Core group (e.g. previously remote development group).

For additional support about workspaces, GitLab team members should reach out to Runners Core group.

Shutdown Strategy & Timeline

Phase 1: Assessment & Communication (Weeks 1-2)

DRI: Development Tooling

• Usage Analysis: analyse cluster usage and curate impact
• Stakeholder Alignment: Coordinate with Runners Core group on messaging and alternatives
• Communication Launch: Post initial announcement on engineering-fyi with clear timeline

Phase 2: Migration Support (Weeks 3-8)

DRI: Core Runners

• Alternative Setup: Provide hands-on migration assistance to high-usage team members
• Documentation: Create step-by-step migration guides for each alternative solution
• Office Hours: Host weekly "migration office hours" for troubleshooting
• Progress Tracking: Monitor migration progress and identify stragglers

Phase 3: Graceful Shutdown (Weeks 9-12)

DRI: Development Tooling

• Final Warnings: Send escalating reminders (4 weeks, 2 weeks, 1 week before shutdown)
• Data Backup: Ensure any critical workspace data is preserved
• Controlled Shutdown: Gradually reduce cluster capacity to encourage migration
• Final Cutoff: Complete shutdown by December 20, 2025

Timeline

Week	Date Range	Activities	Milestone	DRI
1-2	Oct 28 - Nov 8	Usage analysis, stakeholder alignment, initial communication	Communication launched	Developer Tooling
3-4	Nov 11 - Nov 22	Migration guides, office hours setup, individual outreach	Support infrastructure ready	Core Runners
5-6	Nov 25 - Dec 6	Active migration support, progress tracking	50% users migrated	Core Runners
7-8	Dec 9 - Dec 20	Final warnings, data backup, controlled shutdown	100% migration complete	Developer Tooling

Success Metrics

• Migration Rate: Target 90% user migration by Week 6
• Support Tickets: Minimize post-shutdown support requests
• Cost Savings: Achieve planned operational cost reduction
• User Satisfaction: Maintain productivity during transition

Communication

• Prepare a message and post it on engineering-fyi after aligning with Runners Core group (e.g. previously remote development group).
• Send reminders every month and 2 weeks before the deadline.
• Use multiple channels: Slack notifications, email updates, dedicated support channel
• Executive sponsorship message for resistant users