Merge pull request #2020 from kibra/patch-1

Fix typos in thirdpartyresources.md
This commit is contained in:
devin-donnelly
2016-12-22 19:06:27 -08:00
committed by GitHub
+2 -2
View File
@@ -34,9 +34,9 @@ $ kubectl explain thirdpartyresource
## Creating a ThirdPartyResource
When you user create a new `ThirdPartyResource`, the Kubernetes API Server reacts by creating a new, namespaced RESTful resource path. For now, non-namespaced objects are not supported. As with existing built-in objects, deleting a namespace deletes all custom objects in that namespace. `ThirdPartyResources` themselves are non-namespaced and are available to all namespaces.
When you create a new `ThirdPartyResource`, the Kubernetes API Server reacts by creating a new, namespaced RESTful resource path. For now, non-namespaced objects are not supported. As with existing built-in objects, deleting a namespace deletes all custom objects in that namespace. `ThirdPartyResources` themselves are non-namespaced and are available to all namespaces.
For example, if a save the following `ThirdPartyResource` to `resource.yaml`:
For example, if you save the following `ThirdPartyResource` to `resource.yaml`:
```yaml
apiVersion: extensions/v1beta1