Experimental etcd image for 5k node scalability tests

[wojtek-t]

We have an experimental etcd image that is adding support for "Concurrent Reads". I believe that this should help with the issues that we're currently facing with density test.

I propose to enable this for one or two runs of 5k-node tests. With this we would hit two birds with one stone:

• we will verify the performance impact of that change to Kubernetes
• we will see if the problems with density test are really mostly caused by etcd (in which case they should be mitigated) [i.e. we know those are triggerred by taint manager, but the question is what is happening when processing its LIST pods requests]

/assign @mborsz

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wojtek-t

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/kubernetes/sig-scalability/OWNERS [wojtek-t]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mm4tt]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: cd557962e27b81ff72693f02847caf9301d0f64f

[k8s-ci-robot]

@wojtek-t: Updated the job-config configmap in namespace default using the following files:

• key sig-scalability-release-blocking-jobs.yaml using file config/jobs/kubernetes/sig-scalability/sig-scalability-release-blocking-jobs.yaml

In response to this:

We have an experimental etcd image that is adding support for "Concurrent Reads". I believe that this should help with the issues that we're currently facing with density test.

I propose to enable this for one or two runs of 5k-node tests. With this we would hit two birds with one stone:

• we will verify the performance impact of that change to Kubernetes
• we will see if the problems with density test are really mostly caused by etcd (in which case they should be mitigated) [i.e. we know those are triggerred by taint manager, but the question is what is happening when processing its LIST pods requests]

/assign @mborsz

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.