fix(platform): answer the probes the client-ip layer was refusing - #581
Merged
Merged
Conversation
passcod
approved these changes
Sep 20, 2026
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.
Every new pod is killed by its startup probe. A kubelet reaches the pod directly, so its request carries no
X-Forwarded-For, and under prod'sRightmostXForwardedFortheip_into_responselayer refuses it with 500. The probes only started biting now: before ops#311 they were dropped off the PodSpec, so the running pods have none./livezand/healthzmerge after the layer stack, so they are the one thing the client-ip middleware does not see.