KPO podspec changes for GPU-enabled nodes may cause KPO pod startup failures

Resolved·Degraded performance

Mitigations have been successful. A Platform release that corrects this errant behavior is being worked on now. Issue is resolved.

Tue, Aug 4, 2026, 04:40 PM

(2 weeks ago)

Affected components

Aug 4, 2026, 03:11 PM

04:40 PM

Updates

Resolved

Mitigations have been successful. A Platform release that corrects this errant behavior is being worked on now. Issue is resolved.

Tue, Aug 4, 2026, 04:40 PM

Monitoring

We have rolled back the changes that triggered this issue and are monitoring the issue for confirmation that this issue is resolved.

Tue, Aug 4, 2026, 03:15 PM(1 hour earlier)

Identified

We've identified a change that enabled GPU support for KubernetesPodOperator pods had an unintended side effect when reading pod specs without proper limits set in the expected format.

We're working on a fix, if you notice any unexpected failures for KPO tasks in your Astro deployments, please open a support ticket.

Tue, Aug 4, 2026, 03:11 PM