MK8s - Connectivity Issue

The incident should now be mitigated. The affected storage server is currently getting restored. Once this is completed, redundancy will be fully restored. We do not see any remaining provisioning issues any longer. We are monitoring the situation and the restoration and will then set the incident to resolved.

We have found an issue with one storage server belonging to a redundant storage server pair. Our team is implementing a mitigation.

While provisioning block could be resolved, we are investigating an increased number of storage related errors. We are directing attention to these remaining issues.
Customers could still see issues with attaching storages on Kubernetes.

Storage issue has successfully been resolved, however, job provisioning is currently not progressing successfully. Our provisioning team is investigating.

Our storage team has confirmed the suspected culprit. We are currently mitigating the issue and will monitor provisioning job execution afterwards.

We have narrowed down the issue and believe we have the culprit identified. We are currently confirming the finding.

We have identified a spike in our provisioning engine queue that is a likely root cause for the issues observed. Our provisioning team is informed and has joined the response.

Initial investigation makes a network connectivity issue unlikely. The team is focusing investigation on Managed Kubernetes side.

We are currently investigating a suspected network connectivity issue influencing the MK8s service. We will keep the status page updated with new information as they become available.