We criticized Lambda in ClusterMAX 2.0 for their reliability; in this round of testing, it was one of Lambda’s points of emphasis. Their passive health checks cover the relevant conditions and ultimately autoremediated three errors we simulated during testing. Two synthetic XIDs were autoremediated in less than 15 minutes, and there were connected dashboards to monitor node health. Our test that triggered a genuine XID 79 by performing a PCIe secondary bus reset brought the node into NotReady with no GpuXid, no cordon, and no monitoring visibility on the Kubernetes layer, but it ultimately rejoined the fleet after 2 hours. Our node-reboot tests on the Kubernetes layer also completed without incident.

Great work by the Lambda team on the ClusterMAX Sliver!