Overview - Configuring <strong>ingress</strong> cluster traffic | Networking

This is a cache of https://docs.openshift.com/container-platform/4.1/networking/configuring_ingress_cluster_traffic/overview-traffic.html. It is a snapshot of the page at 2024-11-23T02:45:27.242+0000.

Overview - Configuring <strong>ingress</strong> cluster traffic | Networking | OpenShift Container Platform 4.1

OpenShift Container Platform provides the following methods for communicating from outside the cluster with services running in the cluster.

The methods are recommended, in order or preference:

If you have HTTP/HTTPS, use an ingress Controller.
If you have a TLS-encrypted protocol other than HTTPS. For example, for TLS with the SNI header, use an ingress Controller.
Otherwise, use a Load Balancer, an External IP, or a NodePort.

Method Purpose

Method	Purpose
Use an ingress Controller	Allows access to HTTP/HTTPS traffic and TLS-encrypted protocols other than HTTPS (for example, TLS with the SNI header).
Automatically assign an external IP using a load balancer service	Allows traffic to non-standard ports through an IP address assigned from a pool.
Manually assign an external IP to a service	Allows traffic to non-standard ports through a specific IP address.
Configure a `NodePort`	Expose a service on all nodes in the cluster.

Use an ingress Controller

Allows access to HTTP/HTTPS traffic and TLS-encrypted protocols other than HTTPS (for example, TLS with the SNI header).

Automatically assign an external IP using a load balancer service

Allows traffic to non-standard ports through an IP address assigned from a pool.

Manually assign an external IP to a service

Allows traffic to non-standard ports through a specific IP address.

Configure a NodePort

Expose a service on all nodes in the cluster.

Configuring ingress cluster traffic overview