Merge pull request #24024 from tengqm/api-version-warning
Clarify what API versions mean
This commit is contained in:
commit
c26af3fae7
|
@ -41,6 +41,7 @@ The Kubernetes API server serves an OpenAPI spec via the `/openapi/v2` endpoint.
|
||||||
You can request the response format using request headers as follows:
|
You can request the response format using request headers as follows:
|
||||||
|
|
||||||
<table>
|
<table>
|
||||||
|
<caption style="display:none">Valid request header values for OpenAPI v2 queries</caption>
|
||||||
<thead>
|
<thead>
|
||||||
<tr>
|
<tr>
|
||||||
<th>Header</th>
|
<th>Header</th>
|
||||||
|
@ -68,7 +69,6 @@ You can request the response format using request headers as follows:
|
||||||
<td><em>serves </em><code>application/json</code></td>
|
<td><em>serves </em><code>application/json</code></td>
|
||||||
</tr>
|
</tr>
|
||||||
</tbody>
|
</tbody>
|
||||||
<caption>Valid request header values for OpenAPI v2 queries</caption>
|
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
Kubernetes implements an alternative Protobuf based serialization format that
|
Kubernetes implements an alternative Protobuf based serialization format that
|
||||||
|
@ -102,13 +102,22 @@ to ensure that the API presents a clear, consistent view of system resources
|
||||||
and behavior, and to enable controlling access to end-of-life and/or
|
and behavior, and to enable controlling access to end-of-life and/or
|
||||||
experimental APIs.
|
experimental APIs.
|
||||||
|
|
||||||
Refer to [API versions reference](/docs/reference/using-api/api-overview/#api-versioning)
|
|
||||||
for more details on the API version level definitions.
|
|
||||||
|
|
||||||
To make it easier to evolve and to extend its API, Kubernetes implements
|
To make it easier to evolve and to extend its API, Kubernetes implements
|
||||||
[API groups](/docs/reference/using-api/api-overview/#api-groups) that can be
|
[API groups](/docs/reference/using-api/api-overview/#api-groups) that can be
|
||||||
[enabled or disabled](/docs/reference/using-api/api-overview/#enabling-or-disabling).
|
[enabled or disabled](/docs/reference/using-api/api-overview/#enabling-or-disabling).
|
||||||
|
|
||||||
|
API resources are distinguished by their API group, resource type, namespace
|
||||||
|
(for namespaced resources), and name. The API server may serve the same
|
||||||
|
underlying data through multiple API version and handle the conversion between
|
||||||
|
API versions transparently. All these different versions are actually
|
||||||
|
representations of the same resource. For example, suppose there are two
|
||||||
|
versions `v1` and `v1beta1` for the same resource. An object created by the
|
||||||
|
`v1beta1` version can then be read, updated, and deleted by either the
|
||||||
|
`v1beta1` or the `v1` versions.
|
||||||
|
|
||||||
|
Refer to [API versions reference](/docs/reference/using-api/api-overview/#api-versioning)
|
||||||
|
for more details on the API version level definitions.
|
||||||
|
|
||||||
## API Extension
|
## API Extension
|
||||||
|
|
||||||
The Kubernetes API can be extended in one of two ways:
|
The Kubernetes API can be extended in one of two ways:
|
||||||
|
|
Loading…
Reference in New Issue