Review and update staging use cases doc

[killianmuldoon]

The doc at https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/staging-use-cases.md was last updated in 2019. It is linked from the main cluster api README and goes through a number of use cases / user stories for using the project.

Given how long ago the last update was, and issues that have been pointed out in the doc (e.g. https://github.com/kubernetes-sigs/cluster-api/pull/5702/files/96bb73c3c5461a2381faee2e4622ff3c1370b12b#r752685355).

The staging use cases text should be reviewed and updated to bring readers expectations in line with the realities of cluster api today. A reasonable update is to remove this doc altogether and instead make it part of the cluster api book.

[fabriziopandini]

/milestone v1.1
/kind documentation

[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

[fabriziopandini]

/remove-lifecycle stale

[fabriziopandini]

/help

[k8s-ci-robot]

@fabriziopandini:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

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

In response to this:

/help

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.

[fabriziopandini]

/triage accepted

[dtzar]

It feels like there is overlap with this doc and these areas on the book:

• Personas - This has the angle of "Where CAPI desires to invest resources" versus the article "why does CAPI benefit you as persona".
• Introduction, especially the "Why build Cluster API?" section

My general proposal would be to:

1. Determine the statements in the staging document which are missing from the above pages in the book that we deem are essential. IMO at a quick glance, this should be much less detail/volume than is in there.
2. Merge in those statements into updates to the above two pages in the book.
3. Remove the staging-use-cases article and all references to it.

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[fabriziopandini]

/priority backlog

[fabriziopandini]

/triage accepted
/assign

I will take a look and remove this doc altogether / make it part of the cluster api book.