Conversation
lwr20
force-pushed
the
ttfr
branch
7 times, most recently
from
390feb6 to
e907e12
Compare
lwr20
force-pushed
the
ttfr
branch
13 times, most recently
from
f781541 to
a4f15fa
Compare
Glen-Tigera
approved these changes
May 14, 2025
images/ttfr/pingo.go
Outdated
| return string(b) | ||
| } | ||
|
|
||
| // kubectl debug -it ephemeral-demo --image=busybox:1.28 --target=ephemeral-demo |
Glen-Tigera
reviewed
May 14, 2025
lwr20
commented
May 15, 2025
Member
Author
lwr20
left a comment
lwr20
left a comment
There was a problem hiding this comment.
Needs docs to be updated to explain the new test.
lwr20
force-pushed
the
ttfr
branch
3 times, most recently
from
be076cd to
b414a83
Compare
Glen-Tigera
approved these changes
May 15, 2025
lwr20
force-pushed
the
ttfr
branch
4 times, most recently
from
6550def to
daa4282
Compare
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.
This "time to first response" (TTFR) test spins up a server pod on each node in the cluster, and then spins up client pods on each node in the cluster. The client pods start and send requests to the server pod, and record the amount of time it takes before they get a response. This is sometimes[1] a useful proxy for how long its taking for Calico to program the
rules for that pod (since pods start with a deny-all rule and calico-node must program the correct rules before it can talk to anything).
[1] if
linuxPolicySetupTimeoutSecondsis set in the CalicoNetworkSpec in the Installation resource, then pod startup will be delayed until policy is applied. This can be handy if your application pod wants its first request to always succeed. This is a Calico-specific feature that is not part of the CNI spec. See the Calico documentation for more information on this feature and how to enable it.