kubeadm: increase Etcd election-timeout/heartbeat-interval (align with RKE2) (!9091) · Merge requests · Sylva-projects / sylva-core

What does this MR do and why?

This MR aims to solve the issues that have been encountered with the latency of etcd that can be observed on management clusters during the runs of the CI. The values which are directly targeted are heartbeat-interval and election-timeout as the current values are not suited for our CI infrastructure. WAL fsync p95 (and p99 also) latency can be seen in most of the ASCII graphs found under management-cluster-dump/prometheus-extracts .

At the moment, on kadm etcd is using the default values with heartbeat-interval=100 and election-timeout=1000 which are designed more for low-latency local networks and disks. This MR sets the timeout to 5000 and the heartbeat-interval to 500 in order to allow for a more robust approach over the latency issue.

Additional point:

After a short test that I have run today, I have managed to recreate the spikes of kadm mgmt cluster upgrade locally. They did not lead to a timeout as in CI, but the behavior seem to be the same (oY expressed in seconds):

Source issue: #4579

Test coverage

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`, `okd`, `ck8s`
🐧	Node OS	`ubuntu`, `suse`, `na`, `leapmicro`
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by `mgmt:` or `wkld:` to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	`autorun`, `manual` or `blocking`. Can be used to override global config and start a deployment pipeline the required way

Global config for deployment pipelines

autorun pipelines
allow failure on pipelines
record sylvactl events

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.

Edited Sep 23, 2026 by Tiberiu Mihai

kubeadm: increase Etcd election-timeout/heartbeat-interval (align with RKE2)

What does this MR do and why?

Related reference(s)

Test coverage

CI configuration

Global config for deployment pipelines

Merge request reports