mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-09-14 21:53:52 +00:00
s/An common/A common/
This commit is contained in:
@@ -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
|
||||
|
Reference in New Issue
Block a user