kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update sig-scalability/slos/dns_programming_latency.md 

Co-authored-by: Tim Hockin <thockin@google.com>
This commit is contained in:
Antonio Ojea 2024-03-14 00:11:24 +01:00
parent 434c37c39c
commit f9b6920a0a
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
sig-scalability/slos/dns_programming_latency.md
View File

@ -39,9 +39,11 @@ The reason for doing it this way is feasibility for efficiently computing that:
in 99% of programmers (e.g. iptables). That requires tracking metrics on
per-change base (which we can't do efficiently).
- The SLI is expected to remain constant independently of the number of records, per
example, in a headless service with thousands of pods the SLI for the first and the
last Pod should not exhibit a statistically significant difference.
- The SLI for DNS publishing should remain constant independent of the number of records.
For example, in a headless service with thousands of pods the time between the pod being
assigned an IP and the time DNS makes that IP availabe in the service's A/AAAA record(s)
should be statisitically consistent for the first Pod and the last Pod.
### How to measure the SLI.
There [network programming latency](./network_programming_latency.md) is