Rackspace says an attacker used leaked credentials on 17 November to get into parts of its Rackspace Spot managed Kubernetes platform, where they could act as legitimate users in some customer organisations, create pods and read Kubernetes Secrets. Rackspace revoked tokens and rotated keys, and the console was fully restored on 21 November; it hasn't said how many customers were affected.
Why it matters: If you run workloads on Rackspace Spot, reissue Spot API and refresh tokens, rotate every credential stored in cluster Secrets and check database, registry and Git logs back to 17 November.