[mod] API overview link is dead (#8733)

NG: https://kubernetes.io/docs/reference/api-overview/
OK: https://kubernetes.io/docs/reference/using-api/api-overview/

For example, this page contain dead link.
https://kubernetes.io/docs/reference/

Old page is this, so its change is correct.
https://v1-9.docs.kubernetes.io/docs/reference/api-overview/

Note:
China page don't have this link.
This commit is contained in:
Masaya Aoyama (@amsy810)
2018-06-02 03:48:55 +09:00
committed by k8s-ci-robot
parent 518b6334c5
commit 88a6607e39
5 changed files with 5 additions and 5 deletions
@@ -15,7 +15,7 @@ This page explains [*custom resources*](/docs/concepts/api-extension/custom-reso
{{% capture body %}} {{% capture body %}}
## Custom resources ## Custom resources
A *resource* is an endpoint in the [Kubernetes API](/docs/reference/api-overview/) that stores a collection of [API objects](/docs/concepts/overview/working-with-objects/kubernetes-objects/) of a certain kind. For example, the built-in *pods* resource contains a collection of Pod objects. A *resource* is an endpoint in the [Kubernetes API](/docs/reference/using-api/api-overview/) that stores a collection of [API objects](/docs/concepts/overview/working-with-objects/kubernetes-objects/) of a certain kind. For example, the built-in *pods* resource contains a collection of Pod objects.
A *custom resource* is an extension of the Kubernetes API that is not necessarily available on every A *custom resource* is an extension of the Kubernetes API that is not necessarily available on every
Kubernetes cluster. Kubernetes cluster.
@@ -58,7 +58,7 @@ tools to checkpoint state.
Additionally, the [Kubernetes control Additionally, the [Kubernetes control
plane](/docs/concepts/overview/components/) is built upon the same plane](/docs/concepts/overview/components/) is built upon the same
[APIs](/docs/reference/api-overview/) that are available to developers [APIs](/docs/reference/using-api/api-overview/) that are available to developers
and users. Users can write their own controllers, such as and users. Users can write their own controllers, such as
[schedulers](https://github.com/kubernetes/community/blob/{{< param "githubbranch" >}}/contributors/devel/scheduler.md), [schedulers](https://github.com/kubernetes/community/blob/{{< param "githubbranch" >}}/contributors/devel/scheduler.md),
with [their own with [their own
+1 -1
View File
@@ -9,7 +9,7 @@ weight: 70
## API Reference ## API Reference
* [Kubernetes API Overview](/docs/reference/api-overview/) - Overview of the API for Kubernetes. * [Kubernetes API Overview](/docs/reference/using-api/api-overview/) - Overview of the API for Kubernetes.
* Kubernetes API Versions * Kubernetes API Versions
* [1.10](/docs/reference/generated/kubernetes-api/v1.10/) * [1.10](/docs/reference/generated/kubernetes-api/v1.10/)
* [1.9](https://v1-9.docs.kubernetes.io/docs/reference/) * [1.9](https://v1-9.docs.kubernetes.io/docs/reference/)
@@ -12,7 +12,7 @@ API from various programming languages.
{{% /capture %}} {{% /capture %}}
{{% capture body %}} {{% capture body %}}
To write applications using the [Kubernetes REST API](/docs/reference/api-overview/), To write applications using the [Kubernetes REST API](/docs/reference/using-api/api-overview/),
you do not need to implement the API calls and request/response types yourself. you do not need to implement the API calls and request/response types yourself.
You can use a client library for the programming language you are using. You can use a client library for the programming language you are using.
@@ -20,7 +20,7 @@ This document details the deprecation policy for various facets of the system.
Since Kubernetes is an API-driven system, the API has evolved over time to Since Kubernetes is an API-driven system, the API has evolved over time to
reflect the evolving understanding of the problem space. The Kubernetes API is reflect the evolving understanding of the problem space. The Kubernetes API is
actually a set of APIs, called "API groups", and each API group is actually a set of APIs, called "API groups", and each API group is
independently versioned. [API versions](/docs/reference/api-overview/#api-versioning) fall independently versioned. [API versions](/docs/reference/using-api/api-overview/#api-versioning) fall
into 3 main tracks, each of which has different policies for deprecation: into 3 main tracks, each of which has different policies for deprecation:
| Example | Track | | Example | Track |