test-infra: master blocking jobs should probably be on etcd3
$ 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…
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 23 (22 by maintainers)
/close There are no more jobs that use etcd2
Other issues related to etcd2’s deprecation:
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.
given all other jobs are on default etcd I think we’d just remove this (and use default)
https://github.com/kubernetes/kubernetes/issues/41422
cc @mml @wojtek-t @jpbetz