From c9e46a66e733ca180a38c3763ba82cdb5a44b353 Mon Sep 17 00:00:00 2001 From: Christian Bell Date: Mon, 20 Mar 2017 16:25:47 -0700 Subject: [PATCH] Remove fed ingress known issue for 1.6. It's been fixed. --- docs/tasks/administer-federation/ingress.md | 42 +-------------------- 1 file changed, 2 insertions(+), 40 deletions(-) diff --git a/docs/tasks/administer-federation/ingress.md b/docs/tasks/administer-federation/ingress.md index 410f49d541..5616f0f6ef 100644 --- a/docs/tasks/administer-federation/ingress.md +++ b/docs/tasks/administer-federation/ingress.md @@ -123,13 +123,13 @@ The status of your Federated Ingress will automatically reflect the real-time status of the underlying Kubernetes ingresses, for example: ``` shell -$kubectl --context=federation-cluster describe ingress myingress +kubectl --context=federation-cluster describe ingress myingress Name: myingress Namespace: default Address: 130.211.5.194 TLS: - tls-secret terminates + tls-secret terminates Rules: Host Path Backends ---- ---- -------- @@ -250,44 +250,6 @@ kept running, the Federated Ingress ensures that user traffic is automatically redirected away from the failed cluster to other available clusters. -## Known issue - -GCE L7 load balancer back-ends and health checks are known to "flap"; this is due -to conflicting firewall rules in the federation's underlying clusters, which might override one another. To work around this problem, you can -install the firewall rules manually to expose the targets of all the -underlying clusters in your federation for each Federated Ingress -object. This way, the health checks can consistently pass and the GCE L7 load balancer -can remain stable. You install the rules using the -[`gcloud`](https://cloud.google.com/sdk/gcloud/) command line tool, -[Google Cloud Console](https://console.cloud.google.com) or the -[Google Compute Engine APIs](https://cloud.google.com/compute/docs/reference/latest/). - -You can install these rules using -[`gcloud`](https://cloud.google.com/sdk/gcloud/) as follows: - -```shell -gcloud compute firewall-rules create \ - --source-ranges 130.211.0.0/22 --allow [] \ - --target-tags [] \ - --network -``` - -where: - -1. `firewall-rule-name` can be any name. -2. `[]` is the comma separated list of node ports corresponding to the services that back the Federated Ingress. -3. [] is the comma separated list of the target tags assigned to the nodes in a Kubernetes cluster. -4. is the name of the network where the firewall rule must be installed. - -Example: -```shell -gcloud compute firewall-rules create my-federated-ingress-firewall-rule \ - --source-ranges 130.211.0.0/22 --allow tcp:30301, tcp:30061, tcp:34564 \ - --target-tags my-cluster-1-minion, my-cluster-2-minion \ - --network default -``` - - ## Troubleshooting #### I cannot connect to my cluster federation API