mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
22 lines
1.3 KiB
Plaintext
22 lines
1.3 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * ingress/configuring-ingress-cluster-traffic-ingress-controller.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="nw-using-ingress-and-routes_{context}"]
|
|
= Using Ingress Controllers and routes
|
|
|
|
[role="_abstract"]
|
|
You can use the Ingress Controller to allow external access to an {product-title} cluster. The Ingress Operator manages Ingress Controllers and wildcard DNS.
|
|
|
|
An Ingress Controller is configured to accept external requests and proxy them based on the configured routes. This is limited to HTTP, HTTPS using SNI, and TLS using SNI, which is sufficient for web applications and services that work over TLS with SNI.
|
|
|
|
Work with your administrator to configure an Ingress Controller to accept external requests and proxy them based on the configured routes.
|
|
|
|
The administrator can create a wildcard DNS entry and then set up an Ingress Controller. Then, you can work with the edge Ingress Controller without having to contact the administrators.
|
|
|
|
By default, every Ingress Controller in the cluster can admit any route created in any project in the cluster. The Ingress Controller has the following characteristics:
|
|
|
|
* Has two replicas by default, which means it should be running on two compute nodes.
|
|
* Can be scaled up to have more replicas on more nodes.
|