Clarify “Custom Resources“ concept

[rolfedh]

The subsection title, "Should I add a custom resource to my Kubernetes Cluster?" asks an important question. The content presumably answers this question but doesn't use the term, "custom resource." Instead, it talks about choosing between an aggregated or standalone API. This makes it harder for the reader to determine which of the options corresponds with adding a custom response. I recommend making the connection clearer.

[sftim]

/retitle Clarify “Custom Resources“ concept
/language en
/kind cleanup
/sig api-machinery

[sftim]

Thanks for the report @rolfedh

For anyone picking this up, the table could have a third column that discusses the benefits of CustomResourceDefinition.
The three options are:

• use CustomResourceDefinition (most common choice)
• use API aggregation
• don't integrate your API with Kubernetes at all (eg: you're a cloud provider and you provide a completely different HTTP-based API for managing cloud resources outside Kubernetes)

The discussion about which option to choose really belongs in the page at https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/

[mehabhalodiya]

Hey @sftim !
I would like to work on this issue. Can you help me with descriptive points which should be written in table?

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 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 rotten

[mehabhalodiya]

/remove-lifecycle rotten
/triage accepted