[providers-cncf-kubernetes] Throttle HTTPError during consume pod logs #54761
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AutomationDev85
requested review from
hussein-awala and
jedcunningham
as code owners
boring-cyborg
bot
added
area:providers
provider:cncf-kubernetes
jscheffl
approved these changes
Aug 21, 2025
Contributor
jscheffl
left a comment
jscheffl
left a comment
There was a problem hiding this comment.
Looks good for me. Whereas the readability of the threshold is a bit hard. I am thinking a bit about if it would be possible to put the check for threshold in a small utility that can be shared for more similar cases? But not blocking...
mangal-vairalkar
pushed a commit
to mangal-vairalkar/airflow
that referenced
this pull request
Aug 30, 2025
Co-authored-by: AutomationDev85 <AutomationDev85>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
We use Airflow to scale different kind of tasks and some tasks are running for a long time (> 5 hours) and we are using the KubernetesPodOperator to start a Pod and track the log output of the task. We also use Keda autoscaling to scale up and down the cluster nodes. The issue is that during scale up and down the consume log http connection is disturbed as the API backend also scales up and down. We see then an exception in the log file which confuses the user, as he thinks it has something to do with his task.
As the pod manager already tries to reconnect automatically the idea is to add the HTTPError only it it occurred more than 2 times in 60 seconds to not confuse a user log with exceptions which are ok an handled.
Details of change: