mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
31 lines
1.7 KiB
Plaintext
31 lines
1.7 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * virt/vm_networking/virt-creating-service-vm.adoc
|
|
// * virt/virtual_machines/virt-accessing-vm-ssh.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="virt-about-services_{context}"]
|
|
= About services
|
|
|
|
A Kubernetes service exposes network access for clients to an application running on a set of pods. Services offer abstraction, load balancing, and, in the case of the `NodePort` and `LoadBalancer` types, exposure to the outside world.
|
|
|
|
ClusterIP:: Exposes the service on an internal IP address and as a DNS name to other applications within the cluster. A single service can map to multiple virtual machines. When a client tries to connect to the service, the client's request is load balanced among available backends. `ClusterIP` is the default service type.
|
|
|
|
NodePort:: Exposes the service on the same port of each selected node in the cluster. `NodePort` makes a port accessible from outside the cluster, as long as the node itself is externally accessible to the client.
|
|
|
|
LoadBalancer:: Creates an external load balancer in the current cloud (if supported) and assigns a fixed, external IP address to the service.
|
|
|
|
ifndef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
|
|
[NOTE]
|
|
====
|
|
For on-premise clusters, you can configure a load-balancing service by deploying the MetalLB Operator.
|
|
====
|
|
endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
|
|
|
|
ifdef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
|
|
[NOTE]
|
|
====
|
|
For {product-rosa}, you must use `externalTrafficPolicy: Cluster` when configuring a load-balancing service, to minimize the network downtime during live migration.
|
|
====
|
|
endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
|