New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Increase the max wait time for EndpointCreate API requests #25805
Merged
Conversation
This file contains 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
squeed
added
area/cni
Impacts the Container Networking Interface between Cilium and the orchestrator.
release-note/minor
This PR changes functionality that users may find relevant to operating Cilium.
labels
May 31, 2023
/test |
thorn3r
approved these changes
Jun 2, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice investigation on this one 👍
squeed
force-pushed
the
endpointcreate-wait-longer
branch
from
June 9, 2023 07:52
5a9f0af
to
cd0b6d9
Compare
/test |
christarazi
added
kind/enhancement
This would improve or streamline existing functionality.
area/daemon
Impacts operation of the Cilium daemon.
labels
Jun 15, 2023
In the event that a node has a burst of PodSanboxCreate requests, API requests will pile up. However, we should wait longer for the queue to clear before short-circuting and returing failure. This is because the kubelet has a relatively relaxed timeout for PodSandbox creation -- 4 minutes. Furthermore, if we return a failure here, it is propagated all the way back through containerd to kubelet, which will tear down the entire PodSandbox and try again, which can be expensive. So, increase the maximum queue duration time to 1 minute. That should hopefully give enough time for the queue to clear. Signed-off-by: Casey Callendrello <cdc@isovalent.com>
squeed
force-pushed
the
endpointcreate-wait-longer
branch
from
June 19, 2023 14:03
cd0b6d9
to
4ff1ef8
Compare
/test |
maintainer-s-little-helper
bot
added
the
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
label
Jun 19, 2023
With regards to feature freeze, I argue this is fixing a known bug (and it tweaks a few configs, rather than introducing any sort of new behavior). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/cni
Impacts the Container Networking Interface between Cilium and the orchestrator.
area/daemon
Impacts operation of the Cilium daemon.
kind/bug
This is a bug in the Cilium logic.
kind/enhancement
This would improve or streamline existing functionality.
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
release-note/minor
This PR changes functionality that users may find relevant to operating Cilium.
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.
In the event that a node has a burst of PodSanboxCreate requests, API requests will pile up. However, we should wait longer for the queue to clear before short-circuting and returing failure.
This is because the kubelet has a relatively relaxed timeout for PodSandbox creation -- 4 minutes. Furthermore, if we return a failure here, it is propagated all the way back through containerd to kubelet, which will tear down the entire PodSandbox and try again, which can be expensive.
So, increase the maximum queue duration time to 1 minute. That should hopefully give enough time for the queue to clear.
Fixes: #24361