Skip to content

handle rate limiting of k8s api server in k8s executor#64504

Draft
Nataneljpwd wants to merge 1 commit intoapache:mainfrom
Nataneljpwd:feature/k8s-exec-rate-limit-handling
Draft

handle rate limiting of k8s api server in k8s executor#64504
Nataneljpwd wants to merge 1 commit intoapache:mainfrom
Nataneljpwd:feature/k8s-exec-rate-limit-handling

Conversation

@Nataneljpwd
Copy link
Copy Markdown
Contributor


This PR handles rate limiting in k8s executor, where when a limit is reached, the executor skips pod creation up until the retry-after delay has stated.

Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

  • 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.

@boring-cyborg boring-cyborg bot added area:providers provider:cncf-kubernetes Kubernetes (k8s) provider related issues labels Mar 30, 2026
@Nataneljpwd Nataneljpwd marked this pull request as draft March 30, 2026 19:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:providers provider:cncf-kubernetes Kubernetes (k8s) provider related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant