New PodReadyToStartContainers condition to pod_latency measurement #716
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
rsevilla87
requested review from
afcollins,
jtaleric,
vishnuchalla,
dry923,
josecastillolema and
smalleni
vishnuchalla
reviewed
Nov 8, 2024
vishnuchalla
reviewed
Nov 8, 2024
vishnuchalla
reviewed
Nov 8, 2024
Signed-off-by: Raul Sevilla <[email protected]>
Signed-off-by: Raul Sevilla <[email protected]>
rsevilla87
force-pushed
the
PodReadyToStartContainers
branch
from
f1c4de3 to
bcbbccb
Compare
Signed-off-by: Raul Sevilla <[email protected]>
rsevilla87
force-pushed
the
PodReadyToStartContainers
branch
from
bcbbccb to
c1559bc
Compare
|
cc: @mukrishn |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Type of change
Description
Very interesting new pod condition, enabled by default as of k8s 1.29 (OCP 4.16)
More info at https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-has-network
We can look at it to establish a new KPI directly inherited from CNI performance
Related Tickets & Documents