addons/cert_manager: retries until webhook pods has been created

[rtsp]

What type of PR is this?

/kind bug

What this PR does / why we need it:

cert-manager webhook pods are deployed via the deployment that need a few second delay after applying the manifests until the pods are created.

This cause Cert Manager | Wait for Webhook pods become ready task to failed occasionally with "error: no matching resources found" if it's run too fast because kubectl wait cannot wait for non-exist resources (see kubernetes/kubectl#1516).

kubespray/roles/kubernetes-apps/ingress_controller/cert_manager/tasks/main.yml

Lines 70 to 76 in b958d6e

	- name: Cert Manager | Wait for Webhook pods become ready
	command: "{{ bin_dir }}/kubectl wait po --namespace={{ cert_manager_namespace }} --selector app=webhook --for=condition=Ready --timeout=600s"
	register: cert_manager_webhook_pods_ready
	when: inventory_hostname == groups['kube_control_plane'][0]
	until: cert_manager_webhook_pods_ready is succeeded
	retries: 30
	delay: 10

This fix is using retries..until trick similar to #7842.

Special notes for your reviewer:

This fix should be removed in the future if the kubernetes/kubectl#1516 is resolved.

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Hi @rtsp. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[rtsp]

/retest

failed test not related to code changes

[k8s-ci-robot]

@rtsp: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

failed test not related to code changes

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.

[oomichi]

/ok-to-test
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: floryut, rtsp

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

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