Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] Quickstart troubleshooting #5220

Open
faermanj opened this issue Nov 20, 2024 · 2 comments
Open

[docs] Quickstart troubleshooting #5220

faermanj opened this issue Nov 20, 2024 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@faermanj
Copy link

/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.

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 20, 2024
@k8s-ci-robot
Copy link
Contributor

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@faermanj
Copy link
Author

faermanj commented Dec 5, 2024

Reviewing to summarize action points on next meeting:
https://gist.github.com/faermanj/9e8f8ea06757da257abc86f814482cd3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants