Cluster-api: Cert-Manager-Webhook False(MissingEndpoints)

[enyinna1234]

What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]

I deployed Cert-Manager with the command from the Cluster API book, the developer's guide section(https://cluster-api.sigs.k8s.io/developer/guide.html) - kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v0.11.0/cert-manager.yaml

The next command "kubectl wait --for=condition=Available --timeout=300s apiservice v1beta1.webhook.cert-manager.io" keeps timing out.

Querying for webhook, I get the response below:

ubuntu@sustained-coonhound:~$ sudo kubectl get apiservices | grep webhook
v1beta1.webhook.cert-manager.io cert-manager/cert-manager-webhook False (MissingEndpoints) 69m

What did you expect to happen:
I expected webhook to be available

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Cluster-api version: v0.3.12
• Minikube/KIND version: v0.9.0
• Kubernetes version: (use kubectl version):
  Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-01-13T13:28:09Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
  Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.1", GitCommit:"206bcadf021e76c27513500ca24182692aabd17e", GitTreeState:"clean", BuildDate:"2020-09-14T07:30:52Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}
• OS (e.g. from /etc/os-release): Ubuntu 18.04.5 LTS (Bionic Beaver)

/kind bug
[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels]

[enyinna1234]

I think there's a gap in the developer guide documentation. The Cert-Manager piece appears to be optional because the cert-manager is already deployed by the time one gets to that step. And running the cert-manager installation command again messes things up.

[fabriziopandini]

/remove-kind bug
/kind documentation

/milestone v0.4.0

@enyinna1234 I think this is only a problem due to the developer's guide section still linking to cert-manager v0.11.0, while currently Cluster API uses v0.16.1.

Given that you discovered this problem and you see well acquainted with this guide, what do you think about sending a PR to fix the documentation?

[fabriziopandini]

/help
/good-first-issue

[k8s-ci-robot]

@fabriziopandini:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/help
/good-first-issue

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.

[fmuyassarov]

Hi,
I can send a quick fix for this.
/assign

[fmuyassarov]

@enyinna1234 Let us know if you are still failing to deploy the cert-manager. Thanks.

[enyinna1234]

Thanks, @fmuyassarov. I was able to do more testing. There are 2 issues that I identified with the documentation here:

1. It asks to create a management cluster (https://cluster-api.sigs.k8s.io/developer/guide.html#a-cluster). But creating a management cluster also deploys cert manager. And if the user goes on to deploy cert manager as instructed further down (https://cluster-api.sigs.k8s.io/developer/guide.html#cert-manager), then the user ends up with cert manager problems. Solution? Maybe some text to say that the Cert Manager step is optional.
2. The cert-manager webhook service availability command on there (https://cluster-api.sigs.k8s.io/developer/guide.html#cert-manager) isn't working. It might be best to just link the cert-manager documentation, to guide with installation and testing.