From 8a6fedf1c84d0270cb594f95a6f28256f5eade8d Mon Sep 17 00:00:00 2001 From: Andrew Chen Date: Thu, 30 Mar 2017 14:23:42 -0700 Subject: [PATCH] fix api-reference/v1/definitions links --- docs/admin/node.md | 2 +- .../services-networking/connect-applications-service.md | 2 +- .../run-stateless-ap-replication-controller.md | 2 +- docs/user-guide/pods/index.md | 2 +- docs/user-guide/replication-controller/index.md | 2 +- docs/user-guide/security-context.md | 4 ++-- docs/user-guide/services/index.md | 2 +- 7 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/admin/node.md b/docs/admin/node.md index 1f20c91586..10bbb1ad1d 100644 --- a/docs/admin/node.md +++ b/docs/admin/node.md @@ -256,4 +256,4 @@ on each kubelet where you want to reserve resources. Node is a top-level resource in the Kubernetes REST API. More details about the API object can be found at: [Node API -object](/docs/api-reference/v1/definitions/#_v1_node). +object](/docs/api-reference/v1.6/#node-v1-core). diff --git a/docs/concepts/services-networking/connect-applications-service.md b/docs/concepts/services-networking/connect-applications-service.md index c7351e8f87..3ac55194bb 100644 --- a/docs/concepts/services-networking/connect-applications-service.md +++ b/docs/concepts/services-networking/connect-applications-service.md @@ -64,7 +64,7 @@ This is equivalent to `kubectl create -f` the following yaml: {% include code.html language="yaml" file="nginx-svc.yaml" ghlink="/docs/concepts/services-networking/nginx-svc.yaml" %} -This specification will create a Service which targets TCP port 80 on any Pod with the `run: my-nginx` label, and expose it on an abstracted Service port (`targetPort`: is the port the container accepts traffic on, `port`: is the abstracted Service port, which can be any port other pods use to access the Service). View [service API object](/docs/api-reference/v1/definitions/#_v1_service) to see the list of supported fields in service definition. +This specification will create a Service which targets TCP port 80 on any Pod with the `run: my-nginx` label, and expose it on an abstracted Service port (`targetPort`: is the port the container accepts traffic on, `port`: is the abstracted Service port, which can be any port other pods use to access the Service). View [service API object](/docs/api-reference/v1.6/#service-v1-core) to see the list of supported fields in service definition. Check your Service: ```shell diff --git a/docs/tutorials/stateless-application/run-stateless-ap-replication-controller.md b/docs/tutorials/stateless-application/run-stateless-ap-replication-controller.md index ada0d36efd..a861b37698 100644 --- a/docs/tutorials/stateless-application/run-stateless-ap-replication-controller.md +++ b/docs/tutorials/stateless-application/run-stateless-ap-replication-controller.md @@ -102,7 +102,7 @@ below: section of the Creating Multi-Container Pods page covers required and frequently-used fields. * The entire `spec` schema is documented in the - [Kubernetes API reference](/docs/api-reference/v1/definitions/#_v1_podspec). + [Kubernetes API reference](/docs/api-reference/v1.6/#podspec-v1-core). ### Sample file diff --git a/docs/user-guide/pods/index.md b/docs/user-guide/pods/index.md index 82932a5de4..3c4821aac3 100644 --- a/docs/user-guide/pods/index.md +++ b/docs/user-guide/pods/index.md @@ -193,4 +193,4 @@ spec.containers[0].securityContext.privileged: forbidden '<*>(0xc20b222db0)true' Pod is a top-level resource in the Kubernetes REST API. More details about the API object can be found at: [Pod API -object](/docs/api-reference/v1/definitions/#_v1_pod). +object](/docs/api-reference/v1.6/#pod-v1-core). diff --git a/docs/user-guide/replication-controller/index.md b/docs/user-guide/replication-controller/index.md index d700ec5624..d3fcc6f37f 100644 --- a/docs/user-guide/replication-controller/index.md +++ b/docs/user-guide/replication-controller/index.md @@ -223,7 +223,7 @@ The ReplicationController is intended to be a composable building-block primitiv Replication controller is a top-level resource in the Kubernetes REST API. More details about the API object can be found at: [ReplicationController API -object](/docs/api-reference/v1/definitions/#_v1_replicationcontroller). +object](/docs/api-reference/v1.6/#replicationcontroller-v1-core). ## Alternatives to ReplicationController diff --git a/docs/user-guide/security-context.md b/docs/user-guide/security-context.md index e560687b89..7b7449e22f 100644 --- a/docs/user-guide/security-context.md +++ b/docs/user-guide/security-context.md @@ -29,7 +29,7 @@ spec: level: "s0:c123,c456" ``` -Please refer to the [API documentation](/docs/api-reference/v1/definitions/#_v1_podsecuritycontext) for a detailed listing and +Please refer to the [API documentation](/docs/api-reference/v1.6/#pod-v1-coresecuritycontext) for a detailed listing and description of all the fields available within the pod security context. @@ -82,6 +82,6 @@ spec: ``` Please refer to the -[API documentation](/docs/api-reference/v1/definitions/#_v1_securitycontext) +[API documentation](/docs/api-reference/v1.6/#securitycontext-v1-core) for a detailed listing and description of all the fields available within the container security context. diff --git a/docs/user-guide/services/index.md b/docs/user-guide/services/index.md index 232f9d18b7..ee95609d95 100644 --- a/docs/user-guide/services/index.md +++ b/docs/user-guide/services/index.md @@ -594,7 +594,7 @@ through a load-balancer, though in those cases the client IP does get altered. Service is a top-level resource in the Kubernetes REST API. More details about the API object can be found at: [Service API -object](/docs/api-reference/v1/definitions/#_v1_service). +object](/docs/api-reference/v1.6/#service-v1-core). ## For More Information