2021-07-30: version.gitlab.com and design.gitlab.com experiencing availability issues

Current Status

version.gitlab.com and design.gitlab.com are currently experiencing service degradation due to the GKE cluster it is running on undergoing an upgrade operation.

Timeline

View recent production deployment and configuration events / gcp events (internal only)

All times UTC.

2021-07-30

• 00:33 - GKE cluster operation operation-1627605186640-025301c0 starts, which upgrades the single node-pool behind the version application
• 00:34 - @ggillies receives page https://gitlab.pagerduty.com/incidents/PORLGBC?utm_source=slack&utm_campaign=channel version.gitlab.com
• 00:40 - @ggillies declares incident in Slack.
• 00:41 - page https://gitlab.pagerduty.com/incidents/PORLGBC?utm_source=slack&utm_campaign=channel resolves without intervention
• 00:45 - @ggillies receives page https://gitlab.pagerduty.com/incidents/PATR5ZP?utm_source=slack&utm_campaign=channel for design.gitlab.com
• 00:50 - page https://gitlab.pagerduty.com/incidents/PATR5ZP?utm_source=slack&utm_campaign=channel resolves without intervention

Corrective Actions

Corrective actions should be put here as soon as an incident is mitigated, ensure that all corrective actions mentioned in the notes below are included.

• Create a runbook for design.gitlab.com https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/8273
• Correct SPOF in ingress-nginx in these environments https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/13904

---

Note: In some cases we need to redact information from public view. We only do this in a limited number of documented cases. This might include the summary, timeline or any other bits of information, laid out in out handbook page. Any of this confidential data will be in a linked issue, only visible internally. By default, all information we can share, will be public, in accordance to our transparency value.

Click to expand or collapse the Incident Review section.

Incident Review

• Ensure that the exec summary is completed at the top of the incident issue, the timeline is updated and relevant graphs are included in the summary
• If there are any corrective action items mentioned in the notes on the incident, ensure they are listed in the "Corrective Action" section
• Fill out relevant sections below or link to the meeting review notes that cover these topics

Customer Impact

1. Who was impacted by this incident? (i.e. external customers, internal customers)
   1. ...
2. What was the customer experience during the incident? (i.e. preventing them from doing X, incorrect display of Y, ...)
   1. ...
3. How many customers were affected?
   1. ...
4. If a precise customer impact number is unknown, what is the estimated impact (number and ratio of failed requests, amount of traffic drop, ...)?
   1. ...

What were the root causes?

• ...

Incident Response Analysis

1. How was the incident detected?
   1. ...
2. How could detection time be improved?
   1. ...
3. How was the root cause diagnosed?
   1. ...
4. How could time to diagnosis be improved?
   1. ...
5. How did we reach the point where we knew how to mitigate the impact?
   1. ...
6. How could time to mitigation be improved?
   1. ...
7. What went well?
   1. ...

Post Incident Analysis

1. Did we have other events in the past with the same root cause?
   1. ...
2. Do we have existing backlog items that would've prevented or greatly reduced the impact of this incident?
   1. ...
3. Was this incident triggered by a change (deployment of code or change to infrastructure)? If yes, link the issue.
   1. ...

Lessons Learned

• ...

Guidelines

• Blameless RCA Guideline

Resources

1. If the Situation Zoom room was utilised, recording will be automatically uploaded to Incident room Google Drive folder (private)