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:
committed by
Andrew Chen
parent
ecf490b756
commit
0667180dd4
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user