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

Summary

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

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

• Started

  Aug 4, 2026 · 3:11 PM

• Resolved

  Aug 4, 2026 · 4:40 PM

• Duration

  1h 29m

• Severity

  Minor

• ◆

  Identified

  Aug 4 · 3:11 PM Astro

  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.

• ◉

  Monitoring

  Aug 4 · 3:15 PM Astro

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

• ✓

  Resolved

  Aug 4 · 4:40 PM Astro

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