github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-14 13:45:06 +00:00
Code Issues Projects Releases Wiki Activity

s/An common/A common/

Browse Source
This commit is contained in:
Thien-Thi Nguyen
2015-06-01 15:38:55 +02:00
parent e49467e912
commit d64c5061de
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/services.md
View File

@@ -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 Every `Service` has a `Type` field which defines how the `Service` can be
accessed. Valid values for this field are: 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) 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` 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 Note that while `NodePort`s can be TCP or UDP, `LoadBalancer`s only support TCP