-
Notifications
You must be signed in to change notification settings - Fork 5.1k
remove deprecated proxy-refresh-interval v2 etcd flag #21278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
/ok-to-test |
|
kvm2 driver with docker runtime Times for minikube (PR 21278) start: 50.1s 48.2s 46.7s 48.0s 48.7s Times for minikube ingress: 14.9s 16.0s 16.0s 15.0s 14.5s docker driver with docker runtime Times for minikube ingress: 13.3s 13.3s 12.8s 13.3s 13.8s Times for minikube start: 23.5s 23.6s 23.6s 22.1s 24.9s docker driver with containerd runtime Times for minikube ingress: 22.8s 23.8s 22.7s 22.7s 39.2s Times for minikube start: 23.5s 23.1s 20.3s 25.9s 25.8s |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: medyagh, prezha 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:
Approvers can indicate their approval by writing |
fixes #21261
prereq #21277
closes #21223
notes:
Unable to load cached images...etcd_3.6.1-1in examples belowkubernetes v1.34.0 actually (see #21277 for details) uses etcd v3.6 that deprecated some v2 options, specifically related to the v2 Proxy:
we used to pass the
proxy-refresh-intervaletcd extra arg in kubeadm.k8s.io/v1beta4 ClusterConfiguration (probably a copy/paste from pre-v1beta4 templates), and that will make etcd fail, hence also fail to start k8s v1.34.0+ cluster:after
kvm driver
docker driver