Kubernetes Clusters in NYC3

As of 01:00 UTC, our Engineering team has confirmed the full resolution of the issue impacting our managed Kubernetes service in the NYC3 region. All operations for clusters should now be functioning normally.

If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Our Engineering team has deployed a fix for the issue impacting our Managed Kubernetes service in the NYC3 region. As of 17:50 UTC, all impact has been mitigated and users should no longer experience any issues with our managed Kubernetes service in the NYC3 region. We are monitoring the situation and will post an update once the incident is completely resolved.

Our Engineering team is investigating an issue with Kubernetes clusters in the NYC3 region. During this time, a subset of users will experience errors while communicating with their clusters in the NYC3 region. Specifically, as of 14:10 UTC, users will be unable to load the Kubernetes Dashboard in the Cloud Control Panel, see errors when accessing via kubectl, and/or see unauthorized/500 errors when attempting to establish connectivity.

Any prior workloads running on the cluster are not affected by this incident. Users will not be able to deploy new workloads.

We apologize for the inconvenience and will share an update once we have more information.