Yandex Cloud experienced a minor incident on January 30, 2020 affecting Managed Service for Kubernetes® and ru-central1-b, lasting 2h 13m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 30, 2020, 11:57 AM UTC
We noticed some problems with Kubernetes masters. Some users may not be able to modify or start pods. Developer team is notified and currently investigating this issue.
- identified Jan 30, 2020, 02:31 PM UTC
Issue was solved around 16:00 GMT+3. We will provide details later.
- resolved Jan 31, 2020, 05:38 PM UTC
On January 30th from 13:47 to 16:00 (GMT +3) due to internal network connectivity issues health check of etcd instances for some clusters in the zone ru-central1-b started to work incorrectly. Verification errors caused cyclic restart of etcd, which led to periodic restarts of kube-apiserver, and therefore to temporary unavailability of the Kubernetes API on clusters affected by the incident. At 16:00 (GMT+3) the network problem was fixed, health check leading to the error on the Managed Service for Kubernetes side was improved so that such network problems will no longer cause problems. Regional clusters affected by the incident did not experience accessibility issues.