add etcd 3.5.6-0 to kuebadm supported etcd version

[pacoxu]

What type of PR is this?

/kind bug

What this PR does / why we need it:

Which issue(s) this PR fixes:

[init] Using Kubernetes version: v1.26.0-rc.1
W1201 18:38:22.238280   13854 images.go:80] could not find officially supported version of etcd for Kubernetes v1.26.0-rc.1, falling back to the nearest etcd version (3.5.6-0)

Special notes for your reviewer:

/cc @neolit123
when I test v1.26.0-rc.1, I got this warning during init.
Should we add this like before to avoid the warning message? This would help when new version is released and new alpha version can work with a warning. But we still need to update it IMO.

Does this PR introduce a user-facing change?

None

[k8s-ci-robot]

Please note that we're already in Test Freeze for the release-1.26 branch. This means every merged PR will be automatically fast-forwarded via the periodic ci-fast-forward job to the release branch of the upcoming v1.26.0 release.

Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Thu Dec 1 09:40:53 UTC 2022.

[k8s-ci-robot]

@pacoxu: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[neolit123]

hm, i thought we have logic in kubeadm to check if no new k8s version maps to a etcd version and just use the old one "25: 3.5.6-0"...but maybe i'm wrong.

this seems OK, i perhaps we still have to modify manually.

/lgtm
/approve
/milestone v1.26

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neolit123, pacoxu

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:

• cmd/kubeadm/OWNERS [neolit123]

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

[neolit123]

/kind bug
(missing 1.26 entry for etcd in kubeadm)

[neolit123]

/hold

(pls remove hold if you agree with my above comment)

[pacoxu]

this seems OK, i perhaps we still have to modify manually.

yes, agree.
/unhold
It seems to have no side-effect.