etcd-io/etcd

[robustness tests] Add Watch without PrevKV or ProgressNotify to Kubernetes traffic generator

Open

#20622 opened on Sep 8, 2025

View on GitHub
 (6 comments) (0 reactions) (1 assignee)Go (51,701 stars) (10,352 forks)batch import
area/robustness-testinghelp wantedtype/feature

Description

What would you like to be added?

Kubernetes traffic generator should use Watch without ProgressNotify (like apiserver does for events) and without PrevKV (like it does for compact_rev_key). The latter will also help cover the case of non-recursive watch.

In case of Watches on events resource, traffic generator could also open multiple watch streams within the same gRPC stream to better mimic what apiserver does.

Work on this was partially started in https://github.com/etcd-io/etcd/pull/20577

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
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Go programmingetcd watch semanticsgRPC streaming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
The issue requires adding Watch without ProgressNotify and PrevKV to the Kubernetes traffic generator in etcd. Work was partially started in PR #20577, which should be reviewed first. The changes should mimic how apiserver uses Watch on events resource and cover non recursive watch. Relevant code is likely in the tools/traffic generator directory. Comments on the issue provide some discussion on implementation details.