kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #2020 from kibra/patch-1 

Fix typos in thirdpartyresources.md
reviewable/pr2021/r1^2
devin-donnelly 2016-12-22 19:06:27 -08:00 committed by GitHub
parent 4ab9a935c8 bdf6d77a18
commit 67be6311ee
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/user-guide/thirdpartyresources.md
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