jx: JX3 boot pod fails

During installation, one of the jx-boot pods fails with the following error:

Error from server (InternalError): error when creating "config-root/namespaces/jx/acme-jx/tls-kill-9-uk-p-certificate.yaml": Internal error occurred: failed calling webhook "webhook.cert-manager.io": Post https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s: no endpoints available for service "cert-manager-webhook"
make[1]: *** [versionStream/src/Makefile.mk:280: kubectl-apply] Error 1
error: failed to regenerate: failed to regenerate phase 1: failed to run 'make regen-phase-1' command in directory '.', output: ''
make: *** [versionStream/src/Makefile.mk:240: regen-check] Error 1

This pod does not seem to be garbage collected and it is not clear if the cluster is deployed correctly or not. A jx-install pod runs every 2 minutes and reports:

time="2021-04-22T15:18:05Z" level=info msg="Found instance namespace: jx-git-operator"
time="2021-04-22T15:18:05Z" level=info msg="Kuberhealthy is located in the jx-git-operator namespace."
starting jx-install health checks
successfully reported

It is not clear if this is due to an incomplete install, or if it is intended to be an ongoing health check. If the latter, it should probably be renamed and have modified log wording to indicate its purpose. The existence of these regularly created pods and their associated webhook pods has the effect of obscuring other system activity with background noise.