Incident Library
Applied filters ComponentSecrets storeSymptomService outageFactorAutomation amplificationClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. Symptoms

    At 18:23 UTC on 28 July 2022, PSF Infrastructure got an alert that at least one Vault container in PyPI's Kubernetes cluster was down and needed unsealing. At 18:46 UTC PyPI's backends became unresponsive, and they stayed down until 18:53 UTC.

    Trigger

    From 17:24 UTC the cloud provider automatically replaced several instances of PyPI's Kubernetes cluster because of an unknown failure. All replacements were healthy by 18:20 UTC, but the event reshuffled many pods and restarted Consul and Vault on new nodes.

    Root cause
    Component
    Contributing factor
    Detection

    An alert at 18:23 UTC told PSF Infrastructure that at least one Vault container was down and needed unsealing.

    Remediation
    • Forcefully removed the Consul pod stuck in Terminating so it was recreated and Consul could elect a leader
    • Unsealed the new Vault containers
Check your cluster for this

This case involves Coordination and key-value store and Secrets store. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

By root cause1