Fix: Skip HTTPClientV1 URL randomization when behind real LB #643
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
As per the current
panda-k8sHelm chart,panda-jediandpanda-serverare deployed as separate StatefulSets in different pods and communicate via a Kubernetes service.In this setup, hostname randomisation in
HTTPClientV1causes Panda JEDI components to resolve and call themselves, leading to failed API calls (e.g.job_reassign) and jobs remaining stuck inPENDING.This PR restores the behavior by skipping URL randomisation when
PANDA_BEHIND_REAL_LBis set. This alignsHTTPClientV1with the old client and fixes inter-component communication issues in Kubernetes deployments.