master blocking jobs should probably be on etcd3

[BenTheElder]

$ cat jobs/env/ci-kubernetes-e2e-gci-gce.env
### job-env
# This list should match the list in kubernetes-pull-build-test-e2e-gce.
NUM_NODES=4
# For now explicitly test etcd v2 mode in this suite.
STORAGE_BACKEND=etcd2
TEST_ETCD_IMAGE=2.2.1
TEST_ETCD_VERSION=2.2.1

# Enable the PodSecurityPolicy in tests.
ENABLE_POD_SECURITY_POLICY=true

I'm not sure who decides this or exactly all which jobs should be running what, but other jobs appear to consume this env and my understanding is that kubernetes should be solidly on etcd3 now...

[BenTheElder]

/assign @krzyzacy
please punt to whoever is appropriate to triage which version we should use

[krzyzacy]

/sig storage
/assign @saad-ali @msau42

[ixdy]

kubernetes/kubernetes#41422

cc @mml @wojtek-t @jpbetz

[krzyzacy]

given all other jobs are on default etcd I think we'd just remove this (and use default)

[BenTheElder]

discussed some offline, this should probably be
/sig api-machinery

[wojtek-t]

Personally, I'm fine with removing those jobs.

But at least in theory, we still support etcd v2 (though we are in deprecation period).
So from that point of view we may be forced to still have these tests - so let's wait for @lavalamp and @jpbetz thoughts.

[BenTheElder]

I've discussed this some more in other venues and it sounds like we need to have some etcd2 testing until 1.12, but I think our primary CI and presubmit jobs blocking on otherwise-defaults GCE e2e should actually be completely-defaults with maybe some other dedicated etcd2 testing jobs.

[BenTheElder]

xref: #6114 (comment)

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[BenTheElder]

/remove-lifecycle stale

[BenTheElder]

Per discussion today in #sig-release we will hold on this until q4
/assign
/assign @spiffxp

[spiffxp]

Other issues related to etcd2's deprecation:

• Consider deprecating etcd2 kubernetes#44156
• Communicate etcd2 support deprecation timeline kubernetes#57354

We announced in v1.9 that etcd2 is being deprecated "1.13 or 1.14"

I'm not planning to unpack which of those versions it is just yet. But I will gladly push for it to be 1.13 as we get closer to it.

[spiffxp]

/kind cleanup
/priority important-longterm

[tpepper]

Is this important longterm only?

Or given https://groups.google.com/d/topic/kubernetes-dev/jMPA4JzKiY4/discussion is this something we should be doing NOW critical urgent?

[BenTheElder]

My understanding was that the most recent update from sig-arch stated we'd only be dropping etcd2 support fully by 1.13, at which point we'd want to drop it from testing.

[jpbetz]

That sounds right to me as well.

[tpepper]

sgtm then

[liggitt]

It's been at the top of the release notes as being deprecated and scheduled for removal in 1.13 in 1.10-1.12.

kubernetes/kubernetes#69310 is open to remove etcd2 support and cluster-lifecycle (specifically kops) is working through switching defaults to etcd3 as well.

[BenTheElder]

yeah I've been trying to watch that, @spiffxp was talking about tackling this from the test side the other day I think :^)

[spiffxp]

Yup, just opened a first pass, I'll see if I can give it some time tomorrow

[spiffxp]

/remove-priority important-longterm
/priority important-soon
/milestone v1.13
/sig release
/sig testing

[spiffxp]

/close
There are no more jobs that use etcd2

[k8s-ci-robot]

@spiffxp: Closing this issue.

In response to this:

/close
There are no more jobs that use etcd2

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.