You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "ShivamSharma43 (via GitHub)" <gi...@apache.org> on 2026/10/04 18:05:30 UTC

Re: [I] GKEStartJobOperator / KubernetesJobOperator fail to delete pod after it ends [airflow]

ShivamSharma43 commented on issue #55192:
URL: https://github.com/apache/airflow/issues/55192#issuecomment-5982874409

   I checked this against current `main`: it looks resolved by #67333 ("Fix monitoring-pod leak in KubernetesJobOperator", closes #67332, which describes the same problem). `KubernetesJobOperator.execute()` now runs `post_complete_action` for every monitoring pod in a `finally` block (`_cleanup_monitoring_pods`), so `on_finish_action` is honoured. `execute_complete()` does the same on the deferrable path. `GKEStartJobOperator` subclasses `KubernetesJobOperator` and calls `super().execute()`, so it inherits the fix. This shipped in the cncf.kubernetes provider release after 2026-05-29, so I think this issue can be closed as a duplicate of #67332.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org