[justinpakzad]

---

The EksDeleteClusterOperator and EksDeleteNodegroupOperator both accept waiter_delay and waiter_max_attempts, but they were never forwarded to the waiters in the sync path. This PR propagates those values to the waiters. For cluster_deleted and nodegroup_deleted the waiter's default (30 delay, 40 attempts) matches the operators defaults. The two waiters reached via the force_delete_compute=True path both default to 60 attempts and 30 delay so this would drop the total budget from 30 minutes to 20 minutes when the params aren't set. Additional tests were added to cover the new behavior and the asserts for two of the existing tests were updated.

Was generative AI tooling used to co-author this PR?

• Yes (Claude Sonnet 5)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[o-nikolas]

I think the behaviour change here is fine, can count this as a bug fix. Thoughts @vincbeck

[vincbeck]

Agree, thanks for the fix!