Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Measure and expose DNS programming latency from Kubernetes plugin. #3171
For now metric is measure only for headless services. Informer has been slighlty
1. Why is this pull request needed and what does it do?
Measure and expose DNS programming latency from Kubernetes plugin.
2. Which issues (if any) are related?
3. Which documentation changes (if any) need to be made?
4. Does this introduce a backward incompatible change or deprecation?
Thank you for your contribution. I've just checked the OWNERS files to find a suitable reviewer. This search was successful and I've asked pmoroney (via
@@ Coverage Diff @@ ## master #3171 +/- ## ========================================== + Coverage 55.25% 56.29% +1.03% ========================================== Files 217 218 +1 Lines 10777 10818 +41 ========================================== + Hits 5955 6090 +135 + Misses 4365 4252 -113 - Partials 457 476 +19
For now metric is measure only for headless services. Informer has been slighlty refactored, so the code can measure latency without storing extra fields on Endpoint struct. Signed-off-by: Janek Łukaszewicz <email@example.com> Suggestions from code review Co-Authored-By: Chris O'Haver <firstname.lastname@example.org>