All Systems Operational
Uptime over the past 90 days. View historical uptime.
Cloudera Data Platform (US) Operational
90 days ago
99.99 % uptime
Today
CDP Management Console ? Operational
90 days ago
99.97 % uptime
Today
CDP Workload Manager ? Operational
90 days ago
100.0 % uptime
Today
CDP IAM ? Operational
90 days ago
100.0 % uptime
Today
Cloudera SSO Operational
90 days ago
99.95 % uptime
Today
Cloudera Data Platform (AP) Operational
90 days ago
99.96 % uptime
Today
CDP IAM Operational
90 days ago
100.0 % uptime
Today
CDP Management Console Operational
90 days ago
99.93 % uptime
Today
Cloudera Data Platform (EU) Operational
90 days ago
99.96 % uptime
Today
CDP IAM Operational
90 days ago
100.0 % uptime
Today
CDP Management Console Operational
90 days ago
99.93 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Past Incidents
May 29, 2022

No incidents reported today.

May 28, 2022

No incidents reported.

May 27, 2022

No incidents reported.

May 26, 2022

No incidents reported.

May 25, 2022
Azure Kubernetes (AKS) Cluster Provisioning fails if the subnet(s) in use has an associated user-assigned NAT Gateway.
Resolved - Cloudera will publish a TSB to regarding this issue.
May 25, 13:16 UTC
Identified - Azure Kubernetes (AKS) Cluster Provisioning for CDP Data Services such as CML(Cloudera Machine Learning, CDE(Cloudera Data Engineering), and CDF(Cloudera Data Flow) will fail if the subnet(s) in use has an associated NAT Gateway.

Microsoft made a change starting from May, wherein creating an AKS cluster using the above Networking setup will fail unless the parameter: outboundType is set to userAssignedNATGateway.

The error is:
status: CREATE_FAILED message: '[error creating cluster] info: containerservice.ManagedClustersClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: Code="SubnetsAssociatedWithNATgatewayWhenOutboundTypeIsStandardLoadBalancer" Message="Subnets ''/subscriptions/017b8edd-1cb1-4c3e-aa2a-2f62880b1d3d/resourceGroups/liftie-test/providers/Microsoft.Network/virtualNetworks/liftie-dev/subnets/liftie-dev.internal.0.westus2, /subscriptions/017b8edd-1cb1-4c3e-aa2a-2f62880b1d3d/resourceGroups/liftie-test/providers/Microsoft.Network/virtualNetworks/liftie-dev/subnets/liftie-dev.internal.0.westus2'' should not have a NAT gateway associated when outbound type is SLB." Target="agentPoolProfile.vnetSubnetID"'

Before the recent change, Azure accepted the default value for outboundType as loadBalancer and allowed the AKS cluster creation.

Note that the above issue is not seen: * If the subnet(s) doesn't have a user-assigned NAT Gateway associated,
- On existing clusters, and
- On the clusters post-upgrade.

References:
- Creating AKS cluster with user-assigned NAT Gateway: https://docs.microsoft.com/en-us/azure/aks/nat-gateway#create-an-aks-cluster-with-a-user-assigned-nat-gateway
- AKS Release Note: https://github.com/Azure/AKS/commit/dfd3e6176bc979d04ef5592513cd0d2ece5146df
- Determining a possible workaround to be recommended is currently in progress.
- Microsoft Case # 2205170010003095 was created as a follow-up.
May 18, 00:36 UTC
May 24, 2022

No incidents reported.

May 23, 2022

No incidents reported.

May 22, 2022

No incidents reported.

May 21, 2022

No incidents reported.

May 20, 2022

No incidents reported.

May 19, 2022

No incidents reported.

May 18, 2022
May 17, 2022

No incidents reported.

May 16, 2022

No incidents reported.

May 15, 2022

No incidents reported.

← Incident History Powered by Atlassian Statuspage