whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update api-concepts.md (#10534)

Browse Source
This commit is contained in:
KevinTHU
2018-10-09 19:51:27 +08:00
committed by k8s-ci-robot
parent 83fc9324e1
commit 20dc612859
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/reference/using-api/api-concepts.md
+2 -2
View File
@@ -164,7 +164,7 @@ For example:
1. List all of the pods on a cluster in the Table format. 1. List all of the pods on a cluster in the Table format.
GET /api/v1/pods GET /api/v1/pods
Accept: application/json;as=Table;v=meta.k8s.io;g=v1beta1 Accept: application/json;as=Table;g=meta.k8s.io;v=v1beta1
--- ---
200 OK 200 OK
Content-Type: application/json Content-Type: application/json
@@ -205,7 +205,7 @@ For API resource types that do not have a custom Table definition on the server,
Table responses are available beginning in version 1.10 of the kube-apiserver. As such, not all API resource types will support a Table response, specifically when using a client against older clusters. Clients that must work against all resource types, or can potentially deal with older clusters, should specify multiple content types in their `Accept` header to support fallback to non-Tabular JSON: Table responses are available beginning in version 1.10 of the kube-apiserver. As such, not all API resource types will support a Table response, specifically when using a client against older clusters. Clients that must work against all resource types, or can potentially deal with older clusters, should specify multiple content types in their `Accept` header to support fallback to non-Tabular JSON:
``` ```
Accept: application/json;as=Table;v=meta.k8s.io;g=v1beta1, application/json Accept: application/json;as=Table;g=meta.k8s.io;v=v1beta1, application/json
``` ```