From 948d545737c21cf55cf8201ee31500388fc88fe3 Mon Sep 17 00:00:00 2001 From: "Olve S. Hansen" Date: Fri, 5 May 2017 23:16:38 +0200 Subject: [PATCH] Added sub-section about internal load balancers (#3136) * Added sub-section about internal load balancers * Title changed to --- docs/concepts/services-networking/service.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/concepts/services-networking/service.md b/docs/concepts/services-networking/service.md index e735def3f9..990795f031 100644 --- a/docs/concepts/services-networking/service.md +++ b/docs/concepts/services-networking/service.md @@ -427,6 +427,21 @@ with the user-specified `loadBalancerIP`. If the `loadBalancerIP` field is not s an ephemeral IP will be assigned to the loadBalancer. If the `loadBalancerIP` is specified, but the cloud provider does not support the feature, the field will be ignored. +#### Internal load balancer on AWS +In a mixed environment it is sometimes necessary to route traffic from services inside the same VPC. +This can be achieved by adding the following annotation to the service: + +```yaml +[...] +metadata: + name: my-service + annotations: + service.beta.kubernetes.io/aws-load-balancer-internal: 0.0.0.0/0 +[...] +``` +In a split-horizon DNS environment you would need two services to be able to route both external and internal traffic to your endpoints. + + #### SSL support on AWS For partial SSL support on clusters running on AWS, starting with 1.3 two annotations can be added to a `LoadBalancer` service: