updating documentation

Author: murali-reddy

Documentation/README.md

@@ -215,6 +215,9 @@ kubectl annotate service my-service "kube-router.io/service.hairpin="
 
 ### Direct server return
 
+Please read below blog on how to user DSR in combination with `--advertise-external-ip` to build highly scalable and available ingress.
+https://cloudnativelabs.github.io/post/2017-11-01-kube-high-available-ingress/
+
 You can enable DSR(Direct Server Return) functionality per service. When enabled service endpoint
 will directly respond to the client by passign the service proxy. When DSR is enabled Kube-router 
 will uses LVS's tunneling mode to achieve this.

README.md

@@ -62,7 +62,11 @@ will fit in perfectly. From a simple full node-to-node mesh to per-node peering
 configurations, most routing needs can be attained. The configuration is
 Kubernetes native (annotations) just like the rest of kube-router, so use the
 tools you already know! Since kube-router uses GoBGP, you have access to a
-modern BGP API platform as well right out of the box.
+modern BGP API platform as well right out of the box. Kube-router also provides
+a way to expose services outside the cluster by advertising ClusterIP and externalIPs to
+configured BGP peers. Kube-routes also support MD5 password based authentication and
+uses strict export policies so you can be assured routes are advertised to underlay
+only as you intended.
 
 For more details please refer to the [BGP documentation](Documentation/bgp.md).