Improve troubleshooting guide for Cluster API

[killianmuldoon]

The CAPI book currently has a troubleshooting page with a guide focused on the Quick Start.

https://cluster-api.sigs.k8s.io/user/troubleshooting.html

It would be great to have a more fully featured troubleshooting guide that takes users through the process of troubleshooting issues in Cluster API. Steps could, for example, include - looking at clusterctl describe, looking at conditions, reviewing the logs etc.

The idea is that this would form a set of steps which would be a go-to for users trying to deal with a non-working cluster.

/area book
/kind cleanup

[k8s-ci-robot]

@killianmuldoon: The label(s) area/book cannot be applied, because the repository doesn't have them.

In response to this:

The CAPI book currently has a troubleshooting page with a guide focused on the Quick Start.

https://cluster-api.sigs.k8s.io/user/troubleshooting.html

It would be great to have a more fully featured troubleshooting guide that takes users through the process of troubleshooting issues in Cluster API. Steps could, for example, include - looking at clusterctl describe, looking at conditions, reviewing the logs etc.

The idea is that this would form a set of steps which would be a go-to for users trying to deal with a non-working cluster.

/area book
/kind cleanup

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.

[killianmuldoon]

/assign

[killianmuldoon]

/kind documentation

[sbueringer]

/triage accepted

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[killianmuldoon]

/remove-lifecycle stale

Still planning on updating this guide

[killianmuldoon]

/unassign

/help