From 3651e3401b7f6d7f305c01cbba93b0d93f7ea8c5 Mon Sep 17 00:00:00 2001 From: Frederic Giloux Date: Fri, 17 Feb 2023 07:33:41 +0100 Subject: [PATCH] Add answer to the question APIRresourceSchema vs CustomResourceDefinition Signed-off-by: Frederic Giloux --- docs/content/en/concepts/quickstart-tenancy-and-apis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/concepts/quickstart-tenancy-and-apis.md b/docs/content/en/concepts/quickstart-tenancy-and-apis.md index 848e63b2f7a..29be4c3067d 100644 --- a/docs/content/en/concepts/quickstart-tenancy-and-apis.md +++ b/docs/content/en/concepts/quickstart-tenancy-and-apis.md @@ -355,7 +355,7 @@ Yay! Q: Why is there a new `APIResourceSchema` resource type that appears to be very similar to `CustomResourceDefinition`? -A: FIXME +A: An APIResourceSchema defines a single custom API type. It is almost identical to a CRD, but creating an APIResourceSchema instance does not add a usable API to the server. By intentionally decoupling the schema definition from serving, API owners can be more explicit about API evolution. Q: Why do I have to append `/clusters/*/` to the `APIExport` service endpoint URL?