If the etcd member is not found, then it has already been removed, and
kubeadm reset should immediately complete the 'remove-etcd-member'
phase. Previously, the phase would complete only once the
exponential-backoff retry expired, up to 3 minutes duration.

This commit also fixes a semantic error in etcd.GetMemberID. Previously,
the function returned 0 if no member was found, but 0 is not a valid
member ID.

…consistent with kubelet

…ck-of-#118104-upstream-release-1.27

Automated cherry pick of kubernetes#118104: Fix waiting for CRD sync at server start

…ck-of-#118069-upstream-release-1.27

Automated cherry pick of kubernetes#118069: kubeadm: fix a bug where the static pod changes detection

…-pick-of-#118156-upstream-release-1.27

Automated cherry pick of kubernetes#118156: update webhook test to go 1.21

Applying it to the entire spec included cleaning up, which makes predicting the
acceptable duration harder because it includes code not owned by the test
itself. It's better to specify a timeout only for the test code itself.

the e2e framwork use active loops to wait for certain async operations,
these loops need to retry on some operations and fail in others.

For the functions that depend on some operations to happen, the
apiserver may return 503 errors until that specific service is
available, so we should retry on those too.

Change-Id: Ib3d194184f6385b9d3d151c7055f27c97c21c3ff

Signed-off-by: guangli.bao <guangli.bao@daocloud.io>

…-of-#118200-upstream-release-1.27

Automated cherry pick of kubernetes#118200: e2e: apply timeout for CSI Storage Capacity test only to node

…k-of-#117586-upstream-release-1.27

Automated cherry pick of kubernetes#117586: Add DisruptionTarget condition when preempting for critical

Signed-off-by: Rita Zhang <rita.z.zhang@gmail.com>

…-of-#118256-upstream-release-1.27

Automated cherry pick of kubernetes#118256: e2e framework retry on Service unavailable errors

…y-pick-of-#117792-kubernetes#117724-upstream-release-1.27

Automated cherry pick of kubernetes#117792: kubeadm: Use internal etcd client through an interface
kubernetes#117724: kubeadm: Make etcd member removal idempotent

Since kube-proxy in LocalModeNodeCIDR needs to obtain the PodCIDR
assigned to the node it watches for the Node object.

However, kube-proxy startup process requires to have these watches in
different places, that opens the possibility of having a race condition
if the same node is recreated and a different PodCIDR is assigned.

Initializing the second watch with the value obtained in the first one
allows us to detect this situation.

Change-Id: I6adeedb6914ad2afd3e0694dcab619c2a66135f8
Signed-off-by: Antonio Ojea <aojea@google.com>

…k-of-#118356-upstream-release-1.27

Automated cherry pick of kubernetes#118356: Add ephemeralcontainer to imagepolicy securityaccount

…-of-#118499-upstream-release-1.27

Automated cherry pick of kubernetes#118499: kube-proxy avoid race condition using LocalModeNodeCIDR

Bump go version in release-1.27

Signed-off-by: Adolfo García Veytia (Puerco) <puerco@chainguard.dev>

Ran hack/update-vendor.sh

Signed-off-by: Adolfo García Veytia (Puerco) <adolfo.garcia@uservers.net>

…ck-of-#117169-upstream-release-1.27

Automated cherry pick of kubernetes#117169: supported version of etcd 3.5.7-0 for Kubernetes v1.27.0-rc.0

[release-1.27] releng/go: Update images, deps and ver to Go 1.20.5

Kubernetes official release v1.27.3