Skip to content

Handing over a provider maintenance or support case

Use this guide when handing over a Google Cloud maintenance event or an open support case affecting CI runners to another responder. The handoff should let them find the provider’s latest answer, know what decision comes next, and reach someone with case access without needing the outgoing responder online.

The handoff template also applies to other providers; the case-finding instructions below are specific to Google Cloud.

This repository is public. Put the filled-in handoff in the confidential issue, merge request or incident that tracks the maintenance, not here.

Copy this list and fill in every line. Write “none” instead of leaving a line out.

  • Provider case: a direct link to the case, not only the number, and the project or organization it was opened under.
  • Maintenance notice: link to the provider notice or Service Health event.
  • Window and scope: start and end in UTC, and the affected regions, zones and runner shards.
  • Decision owner: who decides during the window, and who to ask if they are unavailable.
  • Latest provider answer: link and date.
  • Open questions to the provider: each question that is still unanswered.
  • Contingency: link to the prepared change, the condition for applying it and the condition for reverting it.
  • Provider updates: where they will be posted during the window.

The incoming responder opens the case link and the maintenance notice. If either does not open, the author names someone who has access and will relay provider updates, and says where they will post them.

A support case belongs to the project or organization it was opened under. If it is not listed under the project you expect, look in the organization-wide case list. Viewing cases needs the Tech Support Viewer or Tech Support Editor role. See Getting help with GCP support.