documentation should be updated with octavia amaphora HA options

[Yossi Boaron]

Kuryr-Kubernetes default handler for Kubernetes services and endpoints is openstack loadbalancer.

In addition openshift L7 routing and Kubernetes Ingress engines at Kuryr-Kubernetes are based on openstack loadbalancer.

When octavia is used to provide loadbalancer capability in openstack, we may reach to a single point of failure at Amphora in case octavia wasn't configured to support active/standby loadbalancer topology.

Documentation should be updated

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/527697

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/527697
Committed: https://git.openstack.org/cgit/openstack/kuryr-kubernetes/commit/?id=d76558b303d7a0ca3c1a2722487c63417150b3da
Submitter: Zuul
Branch: master

commit d76558b303d7a0ca3c1a2722487c63417150b3da
Author: Yossi Boaron <email address hidden>
Date: Wed Dec 13 16:27:09 2017 +0200

    Update service documentation with Octavia loadbalancer topology configurtaion.

    When octavia is configured to SINGLE loadbalancer topology, we have a single point of failure
    (Amphora), that's affect both user services and kuryr-kuberenets L7 router module.

    Service documentation is updated with that info.

    Change-Id: I04e2deaf155a43c26d9f008a03b13c05c5286a48
    Closes-Bug: #1737978

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kuryr-kubernetes 0.3.0 release.