You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
kubectl --kubeconfig=./capi-quickstart.kubeconfig get deploy -n cert-manager
NAME READY UP-TO-DATE AVAILABLE AGE
cert-manager 1/1 1 1 7m24s
cert-manager-cainjector 1/1 1 1 7m24s
cert-manager-webhook 1/1 1 1 7m23s
After 10 minutes, init fails with Error: timed out waiting for the condition.
EDIT: I see this when I describe the apiservice:
Message: failing or missing response from https://10.100.0.172:443/apis/webhook.cert-manager.io/v1beta1: Get https://10.100.0.172:443/apis/webhook.cert-manager.io/v1beta1: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
cluster-api-provider-azure version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):
The text was updated successfully, but these errors were encountered:
/kind bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
Use kind cluster to deploy a capz cluster and try to pivot according the instructions at https://cluster-api.sigs.k8s.io/clusterctl/commands/move.html#bootstrap--pivot
The same doesn't repro in an Azure k8s clusters not built by capz (eg. AKS cluster).
Related to kubernetes-sigs/cluster-api#2731
Seeing
init
getting stuck atWaiting for cert-manager to be available...
consistently, even though cert-manager seems to be ready:After 10 minutes,
init
fails withError: timed out waiting for the condition
.EDIT: I see this when I describe the apiservice:
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: