From d64c5061deb380f45bdfee56e03682ba43530491 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Mon, 1 Jun 2015 15:38:55 +0200 Subject: [PATCH] s/An common/A common/ --- docs/services.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/services.md b/docs/services.md index b817531a2f6..b809533e486 100644 --- a/docs/services.md +++ b/docs/services.md @@ -303,10 +303,11 @@ address. Kubernetes supports two ways of doing this: `NodePort`s and Every `Service` has a `Type` field which defines how the `Service` can be accessed. Valid values for this field are: - - ClusterIP: use a cluster-internal IP (portal) only - this is the default - - NodePort: use a cluster IP, but also expose the service on a port on each + + * `ClusterIP`: use a cluster-internal IP (portal) only - this is the default + * `NodePort`: use a cluster IP, but also expose the service on a port on each node of the cluster (the same port on each) - - LoadBalancer: use a ClusterIP and a NodePort, but also ask the cloud + * `LoadBalancer`: use a ClusterIP and a NodePort, but also ask the cloud provider for a load balancer which forwards to the `Service` Note that while `NodePort`s can be TCP or UDP, `LoadBalancer`s only support TCP