From 0667180dd4196a59e6d514b11d6f760349aa89d9 Mon Sep 17 00:00:00 2001 From: Ahmet Alp Balkan Date: Mon, 10 Jul 2017 15:13:19 -0700 Subject: [PATCH] Remove self-links with domain names in docs (#4299) * Remove self-links with domain names in docs Fixes #4191. Skipping the tutorials we import from kubernetes/examples. Signed-off-by: Ahmet Alp Balkan * update federation/index.md user-guide links * update assign-pod-node.md links * update dns-pod-service.md link * update link in jobs-run-to-completion.md * update link in minikube.md * update PS link in minikube.md * update links in stackpoint.md * update links in storage.md * fix link in vsphere.md * fix links in deprecation-policy.md * Update pick-right-solution.md * Update web-ui-dashboard.md * Update ingress.md * Update federation-service-discovery.md * Update user-guide.md * Update expose-external-ip-address.md * Update README.md * Update README.md --- docs/admin/federation/index.md | 10 +++++----- docs/admin/kubelet-tls-bootstrapping.md | 2 +- docs/concepts/configuration/assign-pod-node.md | 10 +++++----- docs/concepts/services-networking/dns-pod-service.md | 2 +- docs/concepts/storage/volumes.md | 2 +- .../workloads/controllers/jobs-run-to-completion.md | 2 +- docs/getting-started-guides/kops.md | 2 +- docs/getting-started-guides/minikube.md | 6 +++--- docs/getting-started-guides/stackpoint.md | 12 ++++++------ docs/getting-started-guides/ubuntu/local.md | 2 +- docs/getting-started-guides/ubuntu/manual.md | 2 +- docs/getting-started-guides/ubuntu/scaling.md | 2 +- docs/getting-started-guides/ubuntu/storage.md | 6 +++--- docs/getting-started-guides/vsphere.md | 2 +- docs/reference/deprecation-policy.md | 4 ++-- docs/setup/pick-right-solution.md | 2 +- .../access-application-cluster/web-ui-dashboard.md | 6 +++--- .../administer-cluster/highly-available-master.md | 2 +- docs/tasks/administer-cluster/ip-masq-agent.md | 4 ++-- docs/tasks/administer-federation/cluster.md | 2 +- docs/tasks/administer-federation/ingress.md | 2 +- .../configure-persistent-volume-storage.md | 2 +- .../configure-pod-container/security-context.md | 2 +- .../tasks/debug-application-cluster/debug-service.md | 2 +- .../tasks/federation/federation-service-discovery.md | 2 +- docs/tasks/inject-data-application/podpreset.md | 2 +- docs/tools/kompose/user-guide.md | 2 +- .../expose-external-ip-address.md | 2 +- docs/user-guide/configmap/README.md | 4 ++-- docs/user-guide/downward-api/README.md | 5 ++--- editdocs.md | 10 +++++----- 31 files changed, 58 insertions(+), 59 deletions(-) diff --git a/docs/admin/federation/index.md b/docs/admin/federation/index.md index e33d177a1a..08cd32c090 100644 --- a/docs/admin/federation/index.md +++ b/docs/admin/federation/index.md @@ -131,12 +131,12 @@ $ federation/deploy/deploy.sh deploy_federation This spins up the federation control components as pods managed by [`Deployments`](/docs/concepts/workloads/controllers/deployment/) on your existing Kubernetes cluster. It also starts a -[`type: LoadBalancer`](http://kubernetes.io/docs/user-guide/services/#type-loadbalancer) -[`Service`](http://kubernetes.io/docs/user-guide/services/) for the +[`type: LoadBalancer`](/docs/concepts/services-networking/service/#type-loadbalancer) +[`Service`](/docs/concepts/services-networking/service/) for the `federation-apiserver` and a -[`PVC`](http://kubernetes.io/docs/user-guide/persistent-volumes/) backed +[`PVC`](/docs/concepts/storage/persistent-volumes/) backed by a dynamically provisioned -[`PV`](http://kubernetes.io/docs/user-guide/persistent-volumes/) for +[`PV`](/docs/concepts/storage/persistent-volumes/) for `etcd`. All these components are created in the `federation` namespace. You can verify that the pods are available by running the following @@ -247,7 +247,7 @@ federation, and in your federation DNS. You can find more details about config maps in general at -[config map](http://kubernetes.io/docs/user-guide/configmap/). +[config map](/docs/tasks/configure-pod-container/configmap/). ### Kubernetes 1.4 and earlier: Setting federations flag on kube-dns-rc diff --git a/docs/admin/kubelet-tls-bootstrapping.md b/docs/admin/kubelet-tls-bootstrapping.md index e0642f940a..a8c9f0c701 100644 --- a/docs/admin/kubelet-tls-bootstrapping.md +++ b/docs/admin/kubelet-tls-bootstrapping.md @@ -38,7 +38,7 @@ name should be as depicted: ``` Add the `--token-auth-file=FILENAME` flag to the kube-apiserver command (in your systemd unit file perhaps) to enable the token file. -See docs [here](http://kubernetes.io/docs/admin/authentication/#static-token-file) for further details. +See docs [here](/docs/admin/authentication/#static-token-file) for further details. ### Client certificate CA bundle diff --git a/docs/concepts/configuration/assign-pod-node.md b/docs/concepts/configuration/assign-pod-node.md index 5cd997078d..799edcce2d 100644 --- a/docs/concepts/configuration/assign-pod-node.md +++ b/docs/concepts/configuration/assign-pod-node.md @@ -348,7 +348,7 @@ pods that shouldn't be running. A few of the use cases are a particular set of users, you can add a taint to those nodes (say, `kubectl taint nodes nodename dedicated=groupName:NoSchedule`) and then add a corresponding toleration to their pods (this would be done most easily by writing a custom -[admission controller](https://kubernetes.io/docs/admin/admission-controllers/)). +[admission controller](/docs/admin/admission-controllers/)). The pods with the tolerations will then be allowed to use the tainted (dedicated) nodes as well as any other nodes in the cluster. If you want to dedicate the nodes to them *and* ensure they *only* use the dedicated nodes, then you should additionally add a label similar @@ -364,14 +364,14 @@ hardware (e.g. `kubectl taint nodes nodename special=true:NoSchedule` or `kubectl taint nodes nodename special=true:PreferNoSchedule`) and adding a corresponding toleration to pods that use the special hardware. As in the dedicated nodes use case, it is probably easiest to apply the tolerations using a custom -[admission controller](https://kubernetes.io/docs/admin/admission-controllers/)). +[admission controller](/docs/admin/admission-controllers/)). For example, the admission controller could use some characteristic(s) of the pod to determine that the pod should be allowed to use the special nodes and hence the admission controller should add the toleration. To ensure that the pods that need the special hardware *only* schedule onto the nodes that have the special hardware, you will need some additional mechanism, e.g. you could represent the special resource using -[opaque integer resources](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/#opaque-integer-resources-alpha-feature) +[opaque integer resources](/docs/concepts/configuration/manage-compute-resources-container/#opaque-integer-resources-alpha-feature) and request it as a resource in the PodSpec, or you could label the nodes that have the special hardware and use node affinity on the pods that need the hardware. @@ -397,7 +397,7 @@ is enabled (you can do this by including `TaintBasedEvictions=true` in `--featur `--feature-gates=FooBar=true,TaintBasedEvictions=true`), the taints are automatically added by the NodeController and the normal logic for evicting pods from nodes based on the Ready NodeCondition is disabled. -(Note: To maintain the existing [rate limiting](https://kubernetes.io/docs/admin/node/#node-controller) +(Note: To maintain the existing [rate limiting](/docs/concepts/architecture/nodes/) behavior of pod evictions due to node problems, the system actually adds the taints in a rate-limited way. This prevents massive pod evictions in scenarios such as the master becoming partitioned from the nodes.) @@ -434,7 +434,7 @@ problems is detected is maintained. The two default tolerations are added by the [DefaultTolerationSeconds admission controller](https://git.k8s.io/kubernetes/plugin/pkg/admission/defaulttolerationseconds). -[DaemonSet](https://kubernetes.io/docs/admin/daemons/) pods are created with +[DaemonSet](/docs/concepts/workloads/controllers/daemonset/) pods are created with `NoExecute` tolerations for `node.alpha.kubernetes.io/unreachable` and `node.alpha.kubernetes.io/notReady` with no `tolerationSeconds`. This ensures that DaemonSet pods are never evicted due to these problems, which matches the behavior when this feature is disabled. diff --git a/docs/concepts/services-networking/dns-pod-service.md b/docs/concepts/services-networking/dns-pod-service.md index 11243f930c..3d88bb322d 100644 --- a/docs/concepts/services-networking/dns-pod-service.md +++ b/docs/concepts/services-networking/dns-pod-service.md @@ -51,7 +51,7 @@ selection from the set. #### SRV records SRV Records are created for named ports that are part of normal or [Headless -Services](https://kubernetes.io/docs/user-guide/services/#headless-services). +Services](/docs/concepts/services-networking/service/#headless-services). For each named port, the SRV record would have the form `_my-port-name._my-port-protocol.my-svc.my-namespace.svc.cluster.local`. For a regular service, this resolves to the port number and the CNAME: diff --git a/docs/concepts/storage/volumes.md b/docs/concepts/storage/volumes.md index c890a7227f..2e96283c01 100644 --- a/docs/concepts/storage/volumes.md +++ b/docs/concepts/storage/volumes.md @@ -575,7 +575,7 @@ More details can be found [here](https://github.com/kubernetes/kubernetes/tree/{ ### vsphereVolume __Prerequisite: Kubernetes with vSphere Cloud Provider configured. -For cloudprovider configuration please refer [vSphere getting started guide](http://kubernetes.io/docs/getting-started-guides/vsphere/).__ +For cloudprovider configuration please refer [vSphere getting started guide](/docs/getting-started-guides/vsphere/).__ A `vsphereVolume` is used to mount a vSphere VMDK Volume into your Pod. The contents of a volume are preserved when it is unmounted. It supports both VMFS and VSAN datastore. diff --git a/docs/concepts/workloads/controllers/jobs-run-to-completion.md b/docs/concepts/workloads/controllers/jobs-run-to-completion.md index fab8192322..8b225969a3 100644 --- a/docs/concepts/workloads/controllers/jobs-run-to-completion.md +++ b/docs/concepts/workloads/controllers/jobs-run-to-completion.md @@ -381,4 +381,4 @@ object, but complete control over what pods are created and how work is assigned ## Cron Jobs -Support for creating Jobs at specified times/dates (i.e. cron) is available in Kubernetes [1.4](https://github.com/kubernetes/kubernetes/pull/11980). More information is available in the [cron job documents](http://kubernetes.io/docs/user-guide/cron-jobs/) +Support for creating Jobs at specified times/dates (i.e. cron) is available in Kubernetes [1.4](https://github.com/kubernetes/kubernetes/pull/11980). More information is available in the [cron job documents](/docs/concepts/workloads/controllers/cron-jobs/) diff --git a/docs/getting-started-guides/kops.md b/docs/getting-started-guides/kops.md index d3d1ad7e86..a8720aa46e 100644 --- a/docs/getting-started-guides/kops.md +++ b/docs/getting-started-guides/kops.md @@ -25,7 +25,7 @@ a building block. kops builds on the kubeadm work. #### Requirements -You must have [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) installed in order for kops to work. +You must have [kubectl](/docs/tasks/tools/install-kubectl/) installed in order for kops to work. #### Installation diff --git a/docs/getting-started-guides/minikube.md b/docs/getting-started-guides/minikube.md index 5d514e4c75..0420af33b6 100644 --- a/docs/getting-started-guides/minikube.md +++ b/docs/getting-started-guides/minikube.md @@ -129,7 +129,7 @@ Remember to turn off the imagePullPolicy:Always, as otherwise Kubernetes won't u The `minikube start` command can be used to start your cluster. This command creates and configures a virtual machine that runs a single-node Kubernetes cluster. -This command also configures your [kubectl](http://kubernetes.io/docs/user-guide/kubectl-overview/) installation to communicate with this cluster. +This command also configures your [kubectl](/docs/user-guide/kubectl-overview/) installation to communicate with this cluster. If you are behind a web proxy, you will need to pass this information in e.g. via @@ -194,7 +194,7 @@ or pass the context on each command like this: `kubectl get pods --context=minik ### Dashboard -To access the [Kubernetes Dashboard](http://kubernetes.io/docs/user-guide/ui/), run this command in a shell after starting minikube to get the address: +To access the [Kubernetes Dashboard](/docs/tasks/access-application-cluster/web-ui-dashboard/), run this command in a shell after starting minikube to get the address: ```shell minikube dashboard ``` @@ -216,7 +216,7 @@ To determine the NodePort for your service, you can use a `kubectl` command like `kubectl get service $SERVICE --output='jsonpath="{.spec.ports[0].nodePort}"'` ## Persistent Volumes -Minikube supports [PersistentVolumes](http://kubernetes.io/docs/user-guide/persistent-volumes/) of type `hostPath`. +Minikube supports [PersistentVolumes](/docs/concepts/storage/persistent-volumes/) of type `hostPath`. These PersistentVolumes are mapped to a directory inside the minikube VM. The Minikube VM boots into a tmpfs, so most directories will not be persisted across reboots (`minikube stop`). diff --git a/docs/getting-started-guides/stackpoint.md b/docs/getting-started-guides/stackpoint.md index a0441a7d9b..4da0d791c2 100644 --- a/docs/getting-started-guides/stackpoint.md +++ b/docs/getting-started-guides/stackpoint.md @@ -38,7 +38,7 @@ Choose any extra options you may want to include with your cluster, then click * You can monitor the status of your cluster and suspend or delete it from [your stackpoint.io dashboard](https://stackpoint.io/#/clusters). -For information on using and managing a Kubernetes cluster on AWS, [consult the Kubernetes documentation](http://kubernetes.io/docs/getting-started-guides/aws/). +For information on using and managing a Kubernetes cluster on AWS, [consult the Kubernetes documentation](/docs/getting-started-guides/aws/). @@ -70,7 +70,7 @@ Choose any extra options you may want to include with your cluster, then click * You can monitor the status of your cluster and suspend or delete it from [your stackpoint.io dashboard](https://stackpoint.io/#/clusters). -For information on using and managing a Kubernetes cluster on GCE, [consult the Kubernetes documentation](http://kubernetes.io/docs/getting-started-guides/gce). +For information on using and managing a Kubernetes cluster on GCE, [consult the Kubernetes documentation](/docs/getting-started-guides/gce/). @@ -103,7 +103,7 @@ Choose any extra options you may want to include with your cluster, then click * You can monitor the status of your cluster and suspend or delete it from [your stackpoint.io dashboard](https://stackpoint.io/#/clusters). -For information on using and managing a Kubernetes cluster on GKE, consult [the official documentation](http://kubernetes.io/docs/). +For information on using and managing a Kubernetes cluster on GKE, consult [the official documentation](/docs/home/). @@ -135,7 +135,7 @@ Choose any extra options you may want to include with your cluster, then click * You can monitor the status of your cluster and suspend or delete it from [your stackpoint.io dashboard](https://stackpoint.io/#/clusters). -For information on using and managing a Kubernetes cluster on DigitalOcean, consult [the official documentation](http://kubernetes.io/docs/). +For information on using and managing a Kubernetes cluster on DigitalOcean, consult [the official documentation](/docs/home/). @@ -168,7 +168,7 @@ Choose any extra options you may want to include with your cluster, then click * You can monitor the status of your cluster and suspend or delete it from [your stackpoint.io dashboard](https://stackpoint.io/#/clusters). -For information on using and managing a Kubernetes cluster on Azure, [consult the Kubernetes documentation](http://kubernetes.io/docs/getting-started-guides/azure/). +For information on using and managing a Kubernetes cluster on Azure, [consult the Kubernetes documentation](/docs/getting-started-guides/azure/). @@ -200,4 +200,4 @@ Choose any extra options you may want to include with your cluster, then click * You can monitor the status of your cluster and suspend or delete it from [your stackpoint.io dashboard](https://stackpoint.io/#/clusters). -For information on using and managing a Kubernetes cluster on Packet, consult [the official documentation](http://kubernetes.io/docs/). +For information on using and managing a Kubernetes cluster on Packet, consult [the official documentation](/docs/home/). diff --git a/docs/getting-started-guides/ubuntu/local.md b/docs/getting-started-guides/ubuntu/local.md index 90bc18f89c..6ef3f8ce74 100644 --- a/docs/getting-started-guides/ubuntu/local.md +++ b/docs/getting-started-guides/ubuntu/local.md @@ -6,7 +6,7 @@ title: Local Kubernetes development with LXD Running Kubernetes locally has obvious development advantages, such as lower cost and faster iteration than constantly deploying and tearing down clusters on a public cloud. Ideally, a Kubernetes developer can spawn all necessary nodes inside local containers and test new configurations as they are committed. This page will show you how to deploy a cluster to LXD containers on a local machine. {% endcapture %} -The purpose of using [LXD](https://linuxcontainers.org/lxd/) on a local machine is to emulate the same deployment that a user would use in a cloud or bare metal. Each node is treated as a machine, with the same characteristics as production. Each node is a separate container, which runs Docker containers and `kubectl` inside (see [Cluster Intro](https://kubernetes.io/docs/tutorials/kubernetes-basics/cluster-intro/) for more info). +The purpose of using [LXD](https://linuxcontainers.org/lxd/) on a local machine is to emulate the same deployment that a user would use in a cloud or bare metal. Each node is treated as a machine, with the same characteristics as production. Each node is a separate container, which runs Docker containers and `kubectl` inside (see [Cluster Intro](/docs/tutorials/kubernetes-basics/cluster-intro/) for more info). {% capture prerequisites %} Install [conjure-up](http://conjure-up.io/), a tool for deploying big software. diff --git a/docs/getting-started-guides/ubuntu/manual.md b/docs/getting-started-guides/ubuntu/manual.md index cc074301a6..6246362531 100644 --- a/docs/getting-started-guides/ubuntu/manual.md +++ b/docs/getting-started-guides/ubuntu/manual.md @@ -123,7 +123,7 @@ through `FLANNEL_BACKEND` and `FLANNEL_OTHER_NET_CONFIG`, as explained in `clust The default setting for `ADMISSION_CONTROL` is right for the latest release of Kubernetes, but if you choose an earlier release then you might want a different setting. See -[the admission control doc](http://kubernetes.io/docs/admin/admission-controllers/#is-there-a-recommended-set-of-plug-ins-to-use) +[the admission control doc](/docs/admin/admission-controllers/#is-there-a-recommended-set-of-plug-ins-to-use) for the recommended settings for various releases. **Note:** When deploying, master needs to be connected to the Internet to download the necessary files. diff --git a/docs/getting-started-guides/ubuntu/scaling.md b/docs/getting-started-guides/ubuntu/scaling.md index 0f1bc050c6..b8ef81c758 100644 --- a/docs/getting-started-guides/ubuntu/scaling.md +++ b/docs/getting-started-guides/ubuntu/scaling.md @@ -22,7 +22,7 @@ The provided Kubernetes master nodes act as a control plane for the cluster. The juju add-unit kubernetes-master -This will add another master node to the control plane. See the [building high-availability clusters](http://kubernetes.io/docs/admin/high-availability) section of the documentation for more information. +This will add another master node to the control plane. See the [building high-availability clusters](/docs/admin/high-availability) section of the documentation for more information. ## Kubernetes workers diff --git a/docs/getting-started-guides/ubuntu/storage.md b/docs/getting-started-guides/ubuntu/storage.md index 9d193fa81b..7c6e192c4e 100644 --- a/docs/getting-started-guides/ubuntu/storage.md +++ b/docs/getting-started-guides/ubuntu/storage.md @@ -60,7 +60,7 @@ juju add-relation kubernetes-master ceph-mon ``` We are now ready to enlist -[Persistent Volumes](http://kubernetes.io/docs/user-guide/persistent-volumes/) +[Persistent Volumes](/docs/concepts/storage/persistent-volumes/) in Kubernetes which our workloads can consume via Persistent Volume (PV) claims. ``` @@ -84,8 +84,8 @@ test 50M RWO Available 10s To consume these Persistent Volumes, your pods will need an associated Persistent Volume Claim with them, and is outside the scope of this README. See the -[Persistent Volumes](http://kubernetes.io/docs/user-guide/persistent-volumes/) +[Persistent Volumes](/docs/concepts/storage/persistent-volumes/) documentation for more information. {% endcapture %} -{% include templates/task.md %} \ No newline at end of file +{% include templates/task.md %} diff --git a/docs/getting-started-guides/vsphere.md b/docs/getting-started-guides/vsphere.md index 9ec2395aab..635aceb3d6 100644 --- a/docs/getting-started-guides/vsphere.md +++ b/docs/getting-started-guides/vsphere.md @@ -33,7 +33,7 @@ vSphere Cloud Provider allows using vSphere managed storage within Kubernetes. I Documentation for how to use vSphere managed storage can be found in the [persistent volumes user -guide](http://kubernetes.io/docs/user-guide/persistent-volumes/#vsphere) and the +guide](/docs/concepts/storage/persistent-volumes/#vsphere) and the [volumes user guide](/docs/concepts/storage/volumes/#vspherevolume) diff --git a/docs/reference/deprecation-policy.md b/docs/reference/deprecation-policy.md index cdc0bb0102..4b6ea5c002 100644 --- a/docs/reference/deprecation-policy.md +++ b/docs/reference/deprecation-policy.md @@ -19,7 +19,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 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 -independently versioned. [API versions](http://kubernetes.io/docs/api/) fall +independently versioned. [API versions](/docs/reference/api-overview/#api-versioning) fall into 3 main tracks, each of which has different policies for deprecation: | Example | Track | @@ -175,7 +175,7 @@ versions are supported in a series of subsequent releases. Consider a hypothetical REST resource named Widget, which was present in API v1 in the above timeline, and which needs to be deprecated. We -[document](http://kubernetes.io/docs/deprecated/) and +[document](/docs/reference/deprecation-policy/) and [announce](https://groups.google.com/forum/#!forum/kubernetes-announce) the deprecation in sync with release X+1. The Widget resource still exists in API version v1 (deprecated) but not in v2alpha1. The Widget resource continues to diff --git a/docs/setup/pick-right-solution.md b/docs/setup/pick-right-solution.md index 31e2dec5f2..c4947a2079 100644 --- a/docs/setup/pick-right-solution.md +++ b/docs/setup/pick-right-solution.md @@ -143,7 +143,7 @@ Below is a table of all of the solutions listed above. IaaS Provider | Config. Mgmt. | OS | Networking | Docs | Support Level -------------------- | ------------ | ------ | ---------- | --------------------------------------------- | ---------------------------- -any | any | multi-support | any CNI | [docs](https://kubernetes.io/docs/getting-started-guides/kubeadm/) | Project ([SIG-cluster-lifecycle](https://git.k8s.io/community/sig-cluster-lifecycle)) +any | any | multi-support | any CNI | [docs](/docs/setup/independent/create-cluster-kubeadm/) | Project ([SIG-cluster-lifecycle](https://git.k8s.io/community/sig-cluster-lifecycle)) GKE | | | GCE | [docs](https://cloud.google.com/container-engine) | Commercial Stackpoint.io | | multi-support | multi-support | [docs](https://stackpoint.io/) | Commercial AppsCode.com | Saltstack | Debian | multi-support | [docs](https://appscode.com/products/cloud-deployment/) | Commercial diff --git a/docs/tasks/access-application-cluster/web-ui-dashboard.md b/docs/tasks/access-application-cluster/web-ui-dashboard.md index a96170b8aa..4b541f9ad7 100644 --- a/docs/tasks/access-application-cluster/web-ui-dashboard.md +++ b/docs/tasks/access-application-cluster/web-ui-dashboard.md @@ -79,7 +79,7 @@ The deploy wizard expects that you provide the following information: A [Deployment](/docs/concepts/workloads/controllers/deployment/) will be created to maintain the desired number of Pods across your cluster. -- **Service** (optional): For some parts of your application (e.g. frontends) you may want to expose a [Service](http://kubernetes.io/docs/user-guide/services/) onto an external, maybe public IP address outside of your cluster (external Service). For external Services, you may need to open up one or more ports to do so. Find more details [here](/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/). +- **Service** (optional): For some parts of your application (e.g. frontends) you may want to expose a [Service](/docs/concepts/services-networking/service/) onto an external, maybe public IP address outside of your cluster (external Service). For external Services, you may need to open up one or more ports to do so. Find more details [here](/docs/tasks/access-application-cluster/configure-cloud-provider-firewall/). Other Services that are only visible from inside the cluster are called internal Services. @@ -119,11 +119,11 @@ track=stable - **Run as privileged**: This setting determines whether processes in [privileged containers](/docs/user-guide/pods/#privileged-mode-for-pod-containers) are equivalent to processes running as root on the host. Privileged containers can make use of capabilities like manipulating the network stack and accessing devices. -- **Environment variables**: Kubernetes exposes Services through [environment variables](http://kubernetes.io/docs/user-guide/environment-guide/). You can compose environment variable or pass arguments to your commands using the values of environment variables. They can be used in applications to find a Service. Values can reference other variables using the `$(VAR_NAME)` syntax. +- **Environment variables**: Kubernetes exposes Services through [environment variables](/docs/tasks/inject-data-application/environment-variable-expose-pod-information/). You can compose environment variable or pass arguments to your commands using the values of environment variables. They can be used in applications to find a Service. Values can reference other variables using the `$(VAR_NAME)` syntax. ### Uploading a YAML or JSON file -Kubernetes supports declarative configuration. In this style, all configuration is stored in YAML or JSON configuration files using the Kubernetes [API](http://kubernetes.io/docs/api/) resource schemas. +Kubernetes supports declarative configuration. In this style, all configuration is stored in YAML or JSON configuration files using the Kubernetes [API](/docs/concepts/overview/kubernetes-api/) resource schemas. As an alternative to specifying application details in the deploy wizard, you can define your application in YAML or JSON files, and upload the files using Dashboard: diff --git a/docs/tasks/administer-cluster/highly-available-master.md b/docs/tasks/administer-cluster/highly-available-master.md index f630a64891..666c2606f3 100644 --- a/docs/tasks/administer-cluster/highly-available-master.md +++ b/docs/tasks/administer-cluster/highly-available-master.md @@ -97,7 +97,7 @@ $ KUBE_GCE_ZONE=replica-zone KUBE_REPLICATE_EXISTING_MASTER=true ./cluster/kube- * Try to place masters replicas in different zones. During a zone failure, all master placed inside the zone will fail. To survive zone failure, also place nodes in multiple zones -(see [multiple-zones](http://kubernetes.io/docs/admin/multiple-zones/) for details). +(see [multiple-zones](/docs/admin/multiple-zones/) for details). * Do not use a cluster with two master replicas. Consensus on a two replica cluster requires both replicas running when changing persistent state. As a result, both replicas are needed and a failure of any replica turns cluster into majority failure state. diff --git a/docs/tasks/administer-cluster/ip-masq-agent.md b/docs/tasks/administer-cluster/ip-masq-agent.md index de7c7b9e69..34c62dac18 100644 --- a/docs/tasks/administer-cluster/ip-masq-agent.md +++ b/docs/tasks/administer-cluster/ip-masq-agent.md @@ -50,7 +50,7 @@ MASQUERADE all -- anywhere anywhere /* ip-masq-agent: ``` -By default, in GCE/GKE starting with Kubernetes version 1.7.0, the ip-masq-agent will run in your cluster. If you are running in another environment, you can add the ip-masq-agent [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/) to your cluster: +By default, in GCE/GKE starting with Kubernetes version 1.7.0, the ip-masq-agent will run in your cluster. If you are running in another environment, you can add the ip-masq-agent [DaemonSet](/docs/concepts/workloads/controllers/daemonset/) to your cluster: {% endcapture %} @@ -65,7 +65,7 @@ kubectl create -f https://github.com/kubernetes-incubator/ip-masq-agent/blob/mas More information can be found in the ip-masq-agent documentation [here](https://github.com/kubernetes-incubator/ip-masq-agent) -In most cases, the default set of rules should be sufficient; however, if this is not the case for your cluster, you can create and apply a [ConfigMap](https://kubernetes.io/docs/tasks/configure-pod-container/configmap/) to customize the IP ranges that are affected. For example, to allow only 10.0.0.0/8 to be considered by the ip-masq-agent, you can create the following [ConfigMap](/docs/tasks/configure-pod-container/configmap/) in a file called "config". +In most cases, the default set of rules should be sufficient; however, if this is not the case for your cluster, you can create and apply a [ConfigMap](/docs/tasks/configure-pod-container/configmap/) to customize the IP ranges that are affected. For example, to allow only 10.0.0.0/8 to be considered by the ip-masq-agent, you can create the following [ConfigMap](/docs/tasks/configure-pod-container/configmap/) in a file called "config". **Note:** It is important that the file is called config since, by default, that will be used as the key for lookup by the ip-masq-agent: ``` diff --git a/docs/tasks/administer-federation/cluster.md b/docs/tasks/administer-federation/cluster.md index e087c4350f..a08919a180 100644 --- a/docs/tasks/administer-federation/cluster.md +++ b/docs/tasks/administer-federation/cluster.md @@ -106,7 +106,7 @@ Currently, only integers are supported with `Gt` or `Lt`. ## Clusters API reference The full clusters API reference is currently in `federation/v1beta1` and more details can be found in details in the -[Federation API reference page](https://kubernetes.io/docs/reference/federation/). +[Federation API reference page](/docs/reference/federation/). {% endcapture %} diff --git a/docs/tasks/administer-federation/ingress.md b/docs/tasks/administer-federation/ingress.md index b994eccbd1..60ef62697c 100644 --- a/docs/tasks/administer-federation/ingress.md +++ b/docs/tasks/administer-federation/ingress.md @@ -300,7 +300,7 @@ Check that: {% endcapture %} {% capture whatsnext %} -* If you need assistance, use one of the [support channels](http://kubernetes.io/docs/troubleshooting/) to seek assistance. +* If you need assistance, use one of the [support channels](/docs/tasks/debug-application-cluster/troubleshooting/) to seek assistance. * For details about use cases that motivated this work, see [Federation proposal](https://git.k8s.io/community/contributors/design-proposals/federation.md). {% endcapture %} diff --git a/docs/tasks/configure-pod-container/configure-persistent-volume-storage.md b/docs/tasks/configure-pod-container/configure-persistent-volume-storage.md index c305af902d..1d8503caac 100644 --- a/docs/tasks/configure-pod-container/configure-persistent-volume-storage.md +++ b/docs/tasks/configure-pod-container/configure-persistent-volume-storage.md @@ -68,7 +68,7 @@ Here is the configuration file for the hostPath PersistentVolume: The configuration file specifies that the volume is at `/tmp/data` on the the cluster's Node. The configuration also specifies a size of 10 gibibytes and an access mode of `ReadWriteOnce`, which means the volume can be mounted as -read-write by a single Node. It defines the [StorageClass name](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#class) +read-write by a single Node. It defines the [StorageClass name](/docs/concepts/storage/persistent-volumes/#class) `manual` for the PersistentVolume, which will be used to bind PersistentVolumeClaim requests to this PersistentVolume. diff --git a/docs/tasks/configure-pod-container/security-context.md b/docs/tasks/configure-pod-container/security-context.md index 287d074c4f..a309d3f395 100644 --- a/docs/tasks/configure-pod-container/security-context.md +++ b/docs/tasks/configure-pod-container/security-context.md @@ -351,7 +351,7 @@ protection, you must ensure each Pod is assigned a unique MCS label. * [Tuning Docker with the newest security enhancements](https://opensource.com/business/15/3/docker-security-tuning) * [Security Contexts design document](https://git.k8s.io/community/contributors/design-proposals/security_context.md) * [Ownership Management design document](https://git.k8s.io/community/contributors/design-proposals/volume-ownership-management.md) -* [Pod Security Policies](https://kubernetes.io/docs/concepts/policy/pod-security-policy/) +* [Pod Security Policies](/docs/concepts/policy/pod-security-policy/) {% endcapture %} diff --git a/docs/tasks/debug-application-cluster/debug-service.md b/docs/tasks/debug-application-cluster/debug-service.md index ca7c980219..981225f55c 100644 --- a/docs/tasks/debug-application-cluster/debug-service.md +++ b/docs/tasks/debug-application-cluster/debug-service.md @@ -567,7 +567,7 @@ There are three things to check: This mostly happens when `kube-proxy` is running in `iptables` mode and Pods are connected with bridge network. The `Kubelet` exposes a `hairpin-mode` -[flag](http://kubernetes.io/docs/admin/kubelet/) that allows endpoints of a Service to loadbalance back to themselves +[flag](/docs/admin/kubelet/) that allows endpoints of a Service to loadbalance back to themselves if they try to access their own Service VIP. The `hairpin-mode` flag must either be set to `hairpin-veth` or `promiscuous-bridge`. diff --git a/docs/tasks/federation/federation-service-discovery.md b/docs/tasks/federation/federation-service-discovery.md index 12ddc3ebe8..03875c3c48 100644 --- a/docs/tasks/federation/federation-service-discovery.md +++ b/docs/tasks/federation/federation-service-discovery.md @@ -380,7 +380,7 @@ Check that: #### This troubleshooting guide did not help me solve my problem -1. Please use one of our [support channels](http://kubernetes.io/docs/troubleshooting/) to seek assistance. +1. Please use one of our [support channels](/docs/tasks/debug-application-cluster/troubleshooting/) to seek assistance. ## For more information diff --git a/docs/tasks/inject-data-application/podpreset.md b/docs/tasks/inject-data-application/podpreset.md index cd7dd8e05d..11928db570 100644 --- a/docs/tasks/inject-data-application/podpreset.md +++ b/docs/tasks/inject-data-application/podpreset.md @@ -23,7 +23,7 @@ See [PodPreset proposal](https://git.k8s.io/community/contributors/design-propos A _Pod Preset_ is an API resource that you can use to inject additional runtime requirements into a Pod at creation time. You use label selectors to specify the Pods to which a given Pod Preset applies. Check out more information on [label -selectors](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors). +selectors](/docs/concepts/overview/working-with-objects/labels/#label-selectors). Using a Pod Preset allows pod template authors to not have to explicitly set information for every pod. This way, authors of pod templates consuming a diff --git a/docs/tools/kompose/user-guide.md b/docs/tools/kompose/user-guide.md index d7bfb71f09..109309e44d 100644 --- a/docs/tools/kompose/user-guide.md +++ b/docs/tools/kompose/user-guide.md @@ -284,7 +284,7 @@ Note: ## Alternate formats -The default `kompose` transformation will generate Kubernetes [Deployments](/docs/concepts/workloads/controllers/deployment/) and [Services](http://kubernetes.io/docs/user-guide/services/), in yaml format. You have alternative option to generate json with `-j`. Also, you can alternatively generate [Replication Controllers](http://kubernetes.io/docs/user-guide/replication-controller/) objects, [Deamon Sets](http://kubernetes.io/docs/admin/daemons/), or [Helm](https://github.com/helm/helm) charts. +The default `kompose` transformation will generate Kubernetes [Deployments](/docs/concepts/workloads/controllers/deployment/) and [Services](/docs/concepts/services-networking/service/), in yaml format. You have alternative option to generate json with `-j`. Also, you can alternatively generate [Replication Controllers](/docs/concepts/workloads/controllers/replicationcontroller/) objects, [Daemon Sets](/docs/concepts/workloads/controllers/daemonset/), or [Helm](https://github.com/helm/helm) charts. ```console $ kompose convert -j diff --git a/docs/tutorials/stateless-application/expose-external-ip-address.md b/docs/tutorials/stateless-application/expose-external-ip-address.md index ccd7a1dfac..d9e8719b42 100644 --- a/docs/tutorials/stateless-application/expose-external-ip-address.md +++ b/docs/tutorials/stateless-application/expose-external-ip-address.md @@ -12,7 +12,7 @@ external IP address. {% capture prerequisites %} - * Install [kubectl](http://kubernetes.io/docs/tasks/kubectl/install/). + * Install [kubectl](/docs/tasks/tools/install-kubectl/). * Use a cloud provider like Google Container Engine or Amazon Web Services to create a Kubernetes cluster. This tutorial creates an diff --git a/docs/user-guide/configmap/README.md b/docs/user-guide/configmap/README.md index 2df57176dd..9a23a29a01 100644 --- a/docs/user-guide/configmap/README.md +++ b/docs/user-guide/configmap/README.md @@ -5,8 +5,8 @@ ## Step Zero: Prerequisites This example assumes you have a Kubernetes cluster installed and running, and that you have -installed the `kubectl` command line tool somewhere in your path. Please see the [getting -started](http://kubernetes.io/docs/getting-started-guides/) for installation instructions for your platform. +installed the `kubectl` command line tool somewhere in your path. Please see [pick the right solution +started](/docs/setup/pick-right-solution/) for installation instructions for your platform. ## Step One: Create the ConfigMap diff --git a/docs/user-guide/downward-api/README.md b/docs/user-guide/downward-api/README.md index 00a27bdcb0..6c2f4fff44 100644 --- a/docs/user-guide/downward-api/README.md +++ b/docs/user-guide/downward-api/README.md @@ -1,11 +1,10 @@ Following these examples, you will create a pod with a container that consumes the pod's name, -namespace, and resource values using the [downward API](http://kubernetes.io/docs/user-guide/downward-api/). +namespace, and resource values using the [downward API](/docs/tasks/inject-data-application/downward-api-volume-expose-pod-information/). ## Step Zero: Prerequisites This example assumes you have a Kubernetes cluster installed and running, and that you have -installed the `kubectl` command line tool somewhere in your path. Please see the [getting -started](http://kubernetes.io/docs/getting-started-guides/) for installation instructions for your platform. +installed the `kubectl` command line tool somewhere in your path. Please see [pick the right solution](/docs/setup/pick-right-solution/) for installation instructions for your platform. ## Step One: Create the pod diff --git a/editdocs.md b/editdocs.md index 0c4e1440be..05dadd90cf 100644 --- a/editdocs.md +++ b/editdocs.md @@ -53,8 +53,8 @@ $( document ).ready(function() { For more information about contributing to the Kubernetes documentation, see: -* [Creating a Documentation Pull Request](http://kubernetes.io/docs/home/contribute/create-pull-request/) -* [Writing a New Topic](http://kubernetes.io/docs/home/contribute/write-new-topic/) -* [Staging Your Documentation Changes](http://kubernetes.io/docs/home/contribute/stage-documentation-changes/) -* [Using Page Templates](http://kubernetes.io/docs/home/contribute/page-templates/) -* [Documentation Style Guide](http://kubernetes.io/docs/home/contribute/style-guide/) +* [Creating a Documentation Pull Request](/docs/home/contribute/create-pull-request/) +* [Writing a New Topic](/docs/home/contribute/write-new-topic/) +* [Staging Your Documentation Changes](/docs/home/contribute/stage-documentation-changes/) +* [Using Page Templates](/docs/home/contribute/page-templates/) +* [Documentation Style Guide](/docs/home/contribute/style-guide/)