We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Since #19137, the kubernetes traffic is unable to send list request because end field is reset.
end
etcd/tests/robustness/client/client.go
Lines 90 to 92 in 2895b19
kubernetes traffic api should send list request during robustness test
Run any robustness tests with kubernetes traffic
client/v3 package doesn't export limit so it's hard to get all the information from Op provided by kubernetes.List.
limit
Op
$ etcd --version # paste output here $ etcdctl version # paste output here
$ etcdctl member list -w table # paste output here $ etcdctl --endpoints=<member list> endpoint status -w table # paste output here
The text was updated successfully, but these errors were encountered:
cc @AwesomePatrol
Sorry, something went wrong.
@AwesomePatrol Can you take a look and confirm if this is an issue?
No branches or pull requests
Bug report criteria
What happened?
Since #19137, the kubernetes traffic is unable to send list request because
end
field is reset.etcd/tests/robustness/client/client.go
Lines 90 to 92 in 2895b19
What did you expect to happen?
kubernetes traffic api should send list request during robustness test
How can we reproduce it (as minimally and precisely as possible)?
Run any robustness tests with kubernetes traffic
Anything else we need to know?
client/v3 package doesn't export
limit
so it's hard to get all the information fromOp
provided by kubernetes.List.Etcd version (please run commands below)
Etcd configuration (command line flags or environment variables)
paste your configuration here
Etcd debug information (please run commands below, feel free to obfuscate the IP address or FQDN in the output)
Relevant log output
The text was updated successfully, but these errors were encountered: