From ea5396f6b7505b837fca335f20a0e78209a1b6e3 Mon Sep 17 00:00:00 2001 From: Cao Shufeng Date: Sat, 8 Sep 2018 18:55:41 +0800 Subject: [PATCH] fix invalid yaml format --- .../migrate-third-party-resource.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/content/en/docs/tasks/access-kubernetes-api/custom-resources/migrate-third-party-resource.md b/content/en/docs/tasks/access-kubernetes-api/custom-resources/migrate-third-party-resource.md index b71e81f39d21f..853add8c3943c 100644 --- a/content/en/docs/tasks/access-kubernetes-api/custom-resources/migrate-third-party-resource.md +++ b/content/en/docs/tasks/access-kubernetes-api/custom-resources/migrate-third-party-resource.md @@ -52,15 +52,15 @@ you **on a best-effort basis**. For example, if your ThirdPartyResource looks like this: - ```yaml - apiVersion: extensions/v1beta1 - kind: ThirdPartyResource - metadata: - name: cron-tab.stable.example.com - description: "A specification of a Pod to run on a cron style schedule" - versions: - - name: v1 - ``` + + apiVersion: extensions/v1beta1 + kind: ThirdPartyResource + metadata: + name: cron-tab.stable.example.com + description: "A specification of a Pod to run on a cron style schedule" + versions: + - name: v1 + A matching CustomResourceDefinition could look like this: