Drop support for etcd2 #622
Description
Feature Description
- One-line feature description (can be used as a release note): Drop support for etcd2
- Primary contact (assignee): @spiffxp
- Responsible SIGs:
- SIG API Machinery
- SIG Release
- SIG Testing
- Design proposal link (community repo): n/a
- Link to e2e and/or unit tests: n/a
- Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred:
- TBD
- Approver (likely from SIG/area to which feature belongs):
- SIG API Machinery: @lavalamp (or whomever they would like to delegate to)
- SIG Release: @AishSundar (or whomever they would like to delegate to)
- SIG Testing: @spiffxp
- Feature target (which target equals to which milestone):
- Stable release target (1.13)
Context:
- Deprecation announcement in CHANGELOG-1.10.md: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.10.md#deprecations
- kubernetes-dev thread: https://groups.google.com/d/msg/kubernetes-dev/DoOl77xjpDA/uZFun65oBwAJ
- etcd v3 as storage backend for APIServer #44 - support for etcd3 was added in 1.5, made stable in 1.6
- Consider deprecating etcd2 kubernetes#44156 - umbrella issue to deprecate/drop etcd2 (note, I feel this is now out of date, and our deprecation has not been nearly as comprehensive, we will just be dropping etcd2 support)
- master blocking jobs should probably be on etcd3 test-infra#7602 - move all testing jobs to etcd3
I'm filing this as a feature issue to raise visibility, but this is intended to more or less be a turning of the crank that was set in motion last year.
/sig api-machinery
/sig release
/sig testing