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 <ahmetb@google.com> * 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
This commit is contained in:
Ahmet Alp Balkan
committed by
Andrew Chen
Andrew Chen
parent
ecf490b756
commit
0667180dd4
@@ -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
|
||||
|
||||
|
||||
@@ -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`).
|
||||
|
||||
@@ -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/).
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -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 %}
|
||||
{% include templates/task.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)
|
||||
|
||||
|
||||
Reference in New Issue
Block a user