Are Custom Resources extensions of the Kubernetes API?

[stephan242]

This is a Bug Report

Problem:
https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/

This article uses descriptions like this (line 1):

Custom resources are extensions of the Kubernetes API.

I'd argue this is incorrect.

Proposed Solution:

It should read:

Custom resources are instances of resource types added to Kubernetes through API extensions.

In other words: Does a Custom Resource provide an API extension? No. Does a Custom Resource Definition provide an API extension? Yes.

Page to Update:
https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/

[kubernetes-prow]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

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.