etcd-io/etcd

[robustness tests] Consider adding Keys, Count to Kubernetes traffic generator

Open

#20.623 geöffnet am 8. Sept. 2025

Auf GitHub ansehen
 (5 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)Go (51.701 Stars) (10.352 Forks)batch import
area/robustness-testinghelp wantedtype/feature

Beschreibung

What would you like to be added?

Kubernetes traffic generator should use Count of Kubernetes-Etcd interface and invoke Ranges with keys_only to better simulate actual Kubernetes traffic.

It seems that keys_only Range calls will be unlikely in the future due to https://github.com/kubernetes/kubernetes/pull/133873.

Work in https://github.com/kubernetes/kubernetes/pull/132355 also replaced calls to Count so it is likely the work on this may no longer be needed/useful.

Why is this needed?

Part of https://github.com/etcd-io/etcd/issues/15820 and https://github.com/etcd-io/etcd/issues/20182

Contributor Guide

Tech Stack
go
Domain
backendtesting
Issue Type
feature
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
4
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
over 1 week
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
needs maintainer response
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
needs investigation
Voraussetzungen
Go programmingUnderstanding of etcd architectureFamiliarity with Kubernetes traffic patterns
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
15
Research-Richtung
This issue proposes adding Keys and Count to the Kubernetes traffic generator in etcd's robustness tests. However, the issue notes that recent PRs (kubernetes/kubernetes#133873 and kubernetes/kubernetes#132355) may make this work unnecessary. First, check the status of those PRs and confirm with maintainers whether this feature is still desired. If so, examine the existing traffic generator code (likely in the tests directory) to understand how to integrate these operations. The discussion in the issue comments may provide further guidance.