k8s-ci-robot
commented
5 days ago This issue is currently awaiting triage.
If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
/kind bug
What steps did you take and what happened: The quickstart doesn't seem to reach a ready cluster with the current instructions.
What did you expect to happen: Workload cluster provisioned and ready
Anything else you would like to add: In the provisioned instance, it seems it's trying to access API on localhost E1120 17:50:20.816379 1861 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused Perhaps it's something I missed
Of course i might have done something wrong, Is that a known error? In any case, I believe a review of the quickstart (and dev guide) would help to make it more resilient.