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

Update federated-ingress.md

Browse Source
This commit is contained in:
devin-donnelly
2016-12-12 14:41:51 -05:00
committed by GitHub
parent 715d5a3c96
commit ea411fb18d
1 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/user-guide/federation/federated-ingress.md
+4 -5
View File
@@ -231,13 +231,12 @@ available clusters.
## Known issue ## Known issue
GCE L7 load balancer backends and healthchecks are known to flap due GCE L7 load balancer back-ends and health checks are known to "flap"; this is due
to the firewall rules from the underlying clusters in federation to conflicting firewall rules in the federation's underlying clusters, which might override one another. To work around this problem, you can
clobbering each other. In order to workaround this problem, you can
install the firewall rules manually to expose the targets of all the install the firewall rules manually to expose the targets of all the
underlying clusters in your federation for each Federated Ingress underlying clusters in your federation for each Federated Ingress
object so that the health checks can pass and GCE L7 load balancer object. This way, the health checks can consistently pass and the GCE L7 load balancer
can remain stable. These rules can be installed using the can remain stable. You install the rules using the
[`gcloud`](https://cloud.google.com/sdk/gcloud/) command line tool, [`gcloud`](https://cloud.google.com/sdk/gcloud/) command line tool,
[Google Cloud Console](https://console.cloud.google.com) or the [Google Cloud Console](https://console.cloud.google.com) or the
[Google Compute Engine APIs](https://cloud.google.com/compute/docs/reference/latest/). [Google Compute Engine APIs](https://cloud.google.com/compute/docs/reference/latest/).