2020-10-16: Error spike due to https_git kubernetes not serving traffic
Summary
Error spike due to https_git Kubernetes not serving traffic
Error spike due to https_git Kubernetes not serving traffic, affecting our Git fleet. Traffic returned to normal values because of the old nodes still being in the rotation as fallback, so no customers affected. We just saw an error spike as Kubernetes started failing to serve traffic.
Timeline
All times UTC.
2020-10-16
- 12:46 - t4cc0re declares incident in Slack using
/incident declare
command.
Click to expand or collapse the Incident Review section.
Incident Review
Summary
- Service(s) affected:
- Team attribution:
- Minutes downtime or degradation:
Metrics
Customer Impact
- Who was impacted by this incident? (i.e. external customers, internal customers)
- What was the customer experience during the incident? (i.e. preventing them from doing X, incorrect display of Y, ...)
- How many customers were affected?
- If a precise customer impact number is unknown, what is the estimated potential impact?
Incident Response Analysis
- How was the event detected?
- How could detection time be improved?
- How did we reach the point where we knew how to mitigate the impact?
- How could time to mitigation be improved?
Post Incident Analysis
- How was the root cause diagnosed?
- How could time to diagnosis be improved?
- Do we have an existing backlog item that would've prevented or greatly reduced the impact of this incident?
- Was this incident triggered by a change (deployment of code or change to infrastructure. If yes, have you linked the issue which represents the change?)?
5 Whys
Lessons Learned
Corrective Actions
Guidelines
Edited by Alberto Ramos