Skip to content

Commit b549327

Browse files
committed
Recommended changes
1 parent cfedb68 commit b549327

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

modules/control-plane-latency.adoc

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,4 +6,15 @@
66
[id="control-plane-latency_{context}"]
77
= Recommended Control Plane latency for reliable clusters
88

9-
We recommend inducing 15ms latency, for the cluster to function normally and to avoid critical alerts such as KubeAPIErrorBudgetBurn and etcdGRPCRequestsSlow.
9+
It's recommended to ensure that the latency between each of the control plane nodes is within 15ms to ensure performant and reliable cluster. Some of the metrics to keep track of includes etcd grpc requests latency, fysnc latency and any critical alerts. Here are the PromQL queries:
10+
11+
+
12+
[source,terminal]
13+
----
14+
histogram_quantile(0.99, sum(rate(grpc_server_handling_seconds_bucket{job=~".*etcd.*", grpc_method!="Defragment", grpc_type="unary"}[5m])) without(grpc_type)) < 0.15
15+
16+
avg_over_time(histogram_quantile(0.99, rate(etcd_disk_wal_fsync_duration_seconds_bucket[2m]))[10m:]) < 1
17+
18+
ALERTS{severity="critical", alertstate="firing"} > 0
19+
20+
----

0 commit comments

Comments
 (0)