🐛 always declare try-or-die-command function in kubeadm-bootstrap-script.sh

[chewong]

What this PR does / why we need it:

When I tried to join a worker node to a 1.31 cluster, I encountered the following error during cloud-init:

[2024-08-22 23:34:18] /usr/local/bin/kubeadm-bootstrap-script: line 111: try-or-die-command: command not found

It appears that before 1.31, we only use try-or-die-command when joining a control plane - https://github.com/kubernetes-sigs/cluster-api/blob/main/bootstrap/kubeadm/internal/cloudinit/kubeadm-bootstrap-script-pre-k8s-1-31.sh#L131-L132. However, for >= 1.31, we use try-or-die-command for kubeadm join regardless of the node role. This PR removes the if condition around the function so that it's available when joining both control plane and worker nodes.

[chewong]

/area bootstrap

[sbueringer]

Thx!

/lgtm
/assign @chrischdi

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 87ab2ceb909327ba232b63ad1205670f840994a6

[sbueringer]

/cherry-pick release-1.8

[k8s-infra-cherrypick-robot]

@sbueringer: once the present PR merges, I will cherry-pick it on top of release-1.8 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.8

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-sigs/prow repository.

[chrischdi]

/approve
/cherry-pick release-1.8

[k8s-infra-cherrypick-robot]

@chrischdi: once the present PR merges, I will cherry-pick it on top of release-1.8 in a new PR and assign it to you.

In response to this:

/approve
/cherry-pick release-1.8

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-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrischdi

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 [chrischdi]

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

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #11090

In response to this:

/cherry-pick release-1.8

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-sigs/prow repository.