""Our monitoring detected a significant capacity loss of about 30 percent of Azure Front Door instances, predominantly across Europe, Middle East, and Africa," Microsoft said. Surely it hadn't rolled out a borked update yet again? Not this time, it seems. The company continued: "We understand that this is due to a dependency on some underlying Kubernetes instances that crashed. We have ruled out any deployments that could have triggered this event.""
"That said, losing almost a third of one's capacity due to crashing Kubernetes instances is less than ideal. A properly-architected solution should be able to recover from whatever woes befall the orchestrator, but apparently not Azure. Social media was its usual supportive self. Some users were attempting to cancel their Game Pass subscriptions following a recent price hike, but were unable to log in due to issues with the service."
Access to Azure Portal, Microsoft Entra, and related services suffered disruptions after a crash in underlying Kubernetes instances that caused about a 30 percent capacity loss of Azure Front Door instances, primarily across Europe, the Middle East, and Africa. Engineers ruled out deployments as the trigger and identified the dependency on crashed Kubernetes instances as the cause. Users experienced login failures and inability to manage services such as Game Pass. Microsoft restarted Kubernetes instances and initiated a failover for the Microsoft 365 Portal to accelerate recovery. Most impacted resources were restored and the service was validated as fully recovered.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]