Use etcd-manager built from etcdadm repo

[justinsb]

We can now use etcd-manager as built from the kubernetes-sigs/etcdadm
repo.

[justinsb]

This image is built from https://github.com/kubernetes-sigs/etcdadm . The intent is that we can make that repo the canonical location. Before merging, we want to get the image built using the k8s staging and image promotion systems.

This image is currently built manually, and is just intended to verify that the version built from the new repo works (i.e. that no problems have been introduced in the repo move)

[justinsb]

cc @hakman

So I finally got the build working and proposed the latest image for promotion

One thing I realized .... I didn't promote the -amd64 and -arm64 tags. Are these needed? If so I can add them to the process (which is a bit of a WIP) and propose another promotion.

Another snafu is (as you pointed out) that it's not as clear which version we are promoting ... we need to tag in the source repo and/or maybe plumb through the version in something like our versions.go.

[hakman]

Thanks @justinsb. This is pretty cool.
There is no need for the -amd64 and the -arm64 tags, at least for us. I don't think we do it for the kOps images either.
Not quite sure what's the best way forward for versions. Tagging in the source repo would be good, but not sure how well this will go long term.

[hakman]

Btw, this is ready from my point of view.
After we merge kubernetes-retired/etcdadm#205 we could switch to v3.1.x.
/lgtm

[hakman]

/test pull-kops-e2e-k8s-containerd-ha

[hakman]

/test pull-kops-e2e-k8s-containerd-ha

[justinsb]

As discussed in office hours, the remaining things shouldn't be blockers for kops adoption, so removing WIP

[hakman]

Thanks @justinsb. I tracked the commits that removed support for etcd v2 in kOps and we are good later with back-porting to 1.20:
#10141
#10245

[hakman]

@justinsb should this also bump the backup image?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman

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:

• OWNERS [hakman]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment