Skip to content

2025-08-22: Scheduled Maintenance: Communications On Gitaly Storage Node Upgrade [GPRD]

Scheduled Maintenance

For IMOC

Timing

🕘 Planned Start: 2025-08-22 12:00 UTC

🕔 Planned End: 2025-08-24 14:00 UTC.

Day Date Upgrade Plan Nodes Remaining
Day 1 Friday, 22nd 2025 Upgrade 10 node (file-hhd nodes) 146
Day 2 Saturday, 23rd 2025 Upgrade 4 batches × 10 nodes 106
Day 3 Sunday, 24th 2025 Upgrade 4 batches × 10 nodes 66
Day 4 Saturday, 30th 2025 Upgrade 4 batches × 10 nodes 26
Day 5.0 Sunday, 31th 2025 Upgrade 3 batches × 10 nodes 0

Infrastructure

🏗️ Affected Infrastructure

Check all that apply:

  • Website
  • API
  • Git (SSH and HTTPS)
  • Container Registry
  • GitLab Pages
  • CI/CD
    • CI/CD - Hosted runners on Linux
    • CI/CD - Hosted runners on Windows
    • CI/CD - Hosted runners on macOS
    • CI/CD - Hosted runners for GitLab community contributions
    • CI/CD - Self-managed runners
  • SAML SSO - GitLab SaaS
  • Background Processing
  • GitLab Customers Portal
  • Support Services
  • packages.gitlab.com
  • version.gitlab.com
  • forum.gitlab.com
  • docs.gitlab.com
  • Product Analytics - Configurator (Beta)
  • Product Analytics - Collector (Beta)
  • Product Analytics - Background processing (Beta)
  • Product Analytics - Queries (Beta)
  • GitLab Duo
  • GitLab agent server for Kubernetes

Should this maintenance appear on our Status Page?

⚠️ If Yes, ping @cmoc in #support_gitlab-com with a link to this issue. ⚠️

  • Yes
  • No

Reminder Emails

We should only send notifications when they contain actionable steps or when customers are impacted. Customer impact may include but are not limited to an anticipated service degradation, downtime. Default to sending no notification when no action is required and/or the maintenance is downtime-free. In cases where we might anticipate downtime, unavailability, or customer action, additional reminders should be considered.

  • Send email notifications now (when the maintenance is created)
  • Send email notifications 72 hours before planned start
  • Send email notifications 24 hours before planned start
  • Send email notifications 1 hour before planned start
  • None of the above

Automation

Automation is enabled for all scheduled maintenance events. Select this to disable automation for this maintenance event.

  • Disable Automation for this scheduled maintenance event

If automation is disabled, CMOC will need to be informed when events start and stop so the active event displays on the status.gitlab.com during the maintenance window.

Will the CMOC need to be actively engaged during the maintenance window?

  • Yes
  • No

Maintenance Summary

The gitaly storage nodes will be upgraded. There may be brief, short-lived disruptions during the upgrade; however, no action is required from customers before or after the upgrade. Retrying operations should be sufficient once the service is restored.

Will it require downtime?

  • Yes
  • No

If yes, details:

For CMOC

Edited by Raynard Omongbale