whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix links. (#2808)

Browse Source
This commit is contained in:
Steve Perry
2017-03-14 11:12:24 -07:00
committed by GitHub
parent 99426f4c55
commit 5e581ccf3e
3 changed files with 9 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tasks/administer-federation/configmap.md
+1 -1
View File
@@ -20,7 +20,7 @@ might also help you create a Federated Kubernetes cluster.
You should also have a basic You should also have a basic
[working knowledge of Kubernetes](/docs/getting-started-guides/) in [working knowledge of Kubernetes](/docs/getting-started-guides/) in
general and [ConfigMaps](/docs/user-guide/ConfigMaps/) in particular. general and [ConfigMaps](/docs/user-guide/configmap/) in particular.
## Overview ## Overview
docs/tasks/administer-federation/daemonset.md
+2 -2
View File
@@ -25,8 +25,8 @@ general and DaemonSets in particular.
## Overview ## Overview
DaemonSets in federation control plane ("Federated Daemonsets" in DaemonSets in federation control plane ("Federated Daemonsets" in
this guide) are very similar to the traditional [Kubernetes this guide) are very similar to the traditional Kubernetes
DaemonSets](/docs/user-guide/DaemonSets/) and provide the same functionality. DaemonSets and provide the same functionality.
Creating them in the federation control plane ensures that they are synchronized Creating them in the federation control plane ensures that they are synchronized
across all the clusters in federation. across all the clusters in federation.
docs/tasks/administer-federation/ingress.md
+6 -7
View File
@@ -11,7 +11,7 @@ originating from web clients around the globe on a single, static IP
address. Low address. Low
network latency, high fault tolerance and easy administration are network latency, high fault tolerance and easy administration are
ensured through intelligent request routing and automatic replica ensured through intelligent request routing and automatic replica
relocation (using [Federated ReplicaSets](docs/user-guide/federation/federated-replicaset.md)). relocation (using [Federated ReplicaSets](/docs/tasks/administer-federation/replicaset/).
Clients are automatically routed, via the shortest network path, to Clients are automatically routed, via the shortest network path, to
the cluster closest to them with available capacity (despite the fact the cluster closest to them with available capacity (despite the fact
that all clients use exactly the same static IP address). The load balancer that all clients use exactly the same static IP address). The load balancer
@@ -173,8 +173,8 @@ Ingresses in the clusters comprising your federation.
To render the underlying ingress shards healthy, we need to add To render the underlying ingress shards healthy, we need to add
backend Pods behind the service upon which the Ingress is based. There are several ways to achieve this, but backend Pods behind the service upon which the Ingress is based. There are several ways to achieve this, but
the easiest is to create a [Federated Service](federated-services.md) and the easiest is to create a Federated Service and
[Federated Replicaset](federated-replicasets.md). Details of how those Federated Replicaset. Details of how those
work are covered in the aforementioned user guides - here we'll simply use them, to work are covered in the aforementioned user guides - here we'll simply use them, to
create appropriately labelled pods and services in the 13 underlying clusters of create appropriately labelled pods and services in the 13 underlying clusters of
our federation: our federation:
@@ -236,8 +236,7 @@ Europe, the request will be routed to the next closest cluster
Ingresses are backed by Services, which are typically (but not always) Ingresses are backed by Services, which are typically (but not always)
backed by one or more ReplicaSets. For Federated Ingresses, it is backed by one or more ReplicaSets. For Federated Ingresses, it is
common practise to use the federated variants of Services and common practise to use the federated variants of Services and
ReplicaSets (see [Federated Services](federated-services.md) and ReplicaSets for this purpose, as
[Federated ReplicaSets](federated-replicasets.md)) for this purpose, as
described above. described above.
In particular, Federated ReplicaSets ensure that the desired number of In particular, Federated ReplicaSets ensure that the desired number of
@@ -331,7 +330,7 @@ Check that:
have been correctly reconfigured, the UID data item in the GLBC have been correctly reconfigured, the UID data item in the GLBC
configmap in each cluster will be identical across all clusters. configmap in each cluster will be identical across all clusters.
See See
[the GLBC docs](https://github.com/kubernetes/contrib/blob/master/ingress/controllers/gce/BETA_LIMITATIONS.md#changing-the-cluster-uid) [the GLBC docs](https://github.com/kubernetes/ingress/blob/7dcb4ae17d5def23d3e9c878f3146ac6df61b09d/controllers/gce/README.md)
for further details. for further details.
If this is not the case, check the logs of your federation If this is not the case, check the logs of your federation
controller manager to determine why this automated reconfiguration controller manager to determine why this automated reconfiguration
@@ -341,7 +340,7 @@ Check that:
successfully. Ingresses created before the reconfiguration of successfully. Ingresses created before the reconfiguration of
your GLBC will interfere with the behavior of your federated your GLBC will interfere with the behavior of your federated
ingresses created after the reconfiguration (see ingresses created after the reconfiguration (see
[the GLBC docs](https://github.com/kubernetes/contrib/blob/master/ingress/controllers/gce/BETA_LIMITATIONS.md#changing-the-cluster-uid) [the GLBC docs](https://github.com/kubernetes/ingress/blob/7dcb4ae17d5def23d3e9c878f3146ac6df61b09d/controllers/gce/README.md)
for further information. To remedy this, for further information. To remedy this,
delete any ingresses created before the cluster joined the delete any ingresses created before the cluster joined the
federation (and had it's GLBC reconfigured), and recreate them if federation (and had it's GLBC reconfigured), and recreate them if