openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

Merge pull request #56612 from openshift-cherrypick-robot/cherry-pick-56089-to-enterprise-4.13

Browse Source 
[enterprise-4.13] CNV-22364: Add note to "Expose port as service" section
This commit is contained in:
Pan Ousley
2023-02-28 17:04:19 -05:00
committed by GitHub
parent a21af0ccc5 191f729b91
commit 2d0846457a
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
modules/virt-about-services.adoc
View File

@@ -6,14 +6,16 @@
[id="virt-about-services_{context}"]
= About services
A Kubernetes _service_ is an abstract way to expose an application running on a set of pods as a network service. Services allow your applications to receive traffic. Services can be exposed in different ways by specifying a `spec.type` in the `Service` object:
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 NodePort and LoadBalancer, exposure to the outside world.
ClusterIP:: Exposes the service on an internal IP address within the cluster. `ClusterIP` is the default service `type`.
Services can be exposed in different ways by specifying a `spec.type` in the `Service` object:
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 service accessible from outside the cluster.
LoadBalancer:: Creates an external load balancer in the current cloud (if supported) and assigns a fixed, external IP address to the service.
+
[NOTE]
====
For on-premise clusters, you can configure a load balancing service by using the MetalLB Operator in layer 2 mode. The BGP mode is not supported. The MetalLB Operator is installed in the `metallb-system` namespace.