From 7c549aeeb9fd3b8eb71b4c57688ec820e08d6669 Mon Sep 17 00:00:00 2001 From: Brendan Burns Date: Thu, 20 Apr 2017 21:04:43 -0700 Subject: [PATCH] Add some more depth to the 3rd party resource documentation. --- docs/concepts/ecosystem/thirdpartyresource.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/concepts/ecosystem/thirdpartyresource.md b/docs/concepts/ecosystem/thirdpartyresource.md index 86f969183b..eeeb54570c 100644 --- a/docs/concepts/ecosystem/thirdpartyresource.md +++ b/docs/concepts/ecosystem/thirdpartyresource.md @@ -63,11 +63,17 @@ Then a new RESTful API endpoint is created at: `/apis/stable.example.com/v1/namespaces//crontabs/...` This endpoint URL can then be used to create and manage custom objects. +The `kind` of these objects will be `CronTab` following the camel case +rules applied to the `metadata.name` of this `ThirdPartyResource` +(`cron-tab.stable.example.com`) ## Creating Custom Objects After the `ThirdPartyResource` object has been created you can create custom objects. Custom objects can contain custom fields. These fields can contain arbitrary JSON. -In the following example, a `cronSpec` and `image` custom fields are set to the custom `CronTab` object. If you save the following YAML to `my-crontab.yaml`: +In the following example, a `cronSpec` and `image` custom fields are set to the custom object of kind `CronTab`. The kind `CronTab` is derived from the +`metadata.name` of the `ThirdPartyResource` object we created above. + +If you save the following YAML to `my-crontab.yaml`: ```yaml apiVersion: "stable.example.com/v1"