Support etcd 3.7.0-rc.0 and allow overriding the etcd version in the scalability scenario - #18458
Conversation
|
/cc @serathius |
…ity scenario Signed-off-by: Jefftree <jeffrey.ying86@live.com>
Signed-off-by: Jefftree <jeffrey.ying86@live.com>
66db949 to
d9af2f8
Compare
|
@Jefftree please explain why you need this in the description. It is unusual to add support for unreleased etcd versions. |
|
Added a block above. We want to soak our scalability tests to use the release candidate ahead of the release. I didn't touch any of the default version selection (still 3.6) as this is a release candidate and should strictly be opt in for the scalability tests.
|
|
OK, it looks good, but will have to wait until we cut the 1.36 branch. It should happen until the end of the week. |
|
sounds good, thank you! |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Adds etcd 3.7.0-rc.0 as a supported version and an optional ETCD_VERSION override in the scalability scenario so scale jobs can test rc candidate.
Opted not to blanket default the 3.7 for all scalability jobs as this is rc candidate, but maybe we should for proper soak.
We are soaking etcd 3.7 ahead of the release. The best way to do that is to integrate with kubernetes scalability test and ensure that we do not find regressions/bugs. Kubernetes is already using the 3.7-rc client library (ref),
The timeline is roughly