mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
53 lines
2.2 KiB
Plaintext
53 lines
2.2 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// *networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-nodeport.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="nw-ingresscontroller-change-external_{context}"]
|
|
= Configuring the Ingress Controller endpoint publishing scope to External
|
|
|
|
[role="_abstract"]
|
|
To expose cluster services to public networks or the internet in {product-title}, configure the Ingress Controller endpoint publishing scope to `External`.
|
|
|
|
When a cluster administrator installs a new cluster without specifying that the cluster is private, the default Ingress Controller is created with a `scope` set to `External`.
|
|
|
|
As an installation or post-installation task, a cluster administrator can configure the Ingress Controller to `Internal`. Additionally, a cluster administrator can change an `Internal` Ingress Controller to `External`.
|
|
|
|
[IMPORTANT]
|
|
====
|
|
On some platforms, it is necessary to delete and recreate the service.
|
|
|
|
Changing the scope can cause disruption to Ingress traffic, potentially for several minutes. This applies to platforms where it is necessary to delete and recreate the service, because the procedure can cause {product-title} to deprovision the existing service load balancer, provision a new one, and update DNS.
|
|
====
|
|
|
|
.Prerequisites
|
|
|
|
* You installed the {oc-first}.
|
|
|
|
.Procedure
|
|
|
|
* To change an `Internal`-scoped Ingress Controller to `External`, enter the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc -n openshift-ingress-operator patch ingresscontrollers/private --type=merge --patch='{"spec":{"endpointPublishingStrategy":{"type":"LoadBalancerService","loadBalancer":{"scope":"External"}}}}'
|
|
----
|
|
|
|
.Verification
|
|
|
|
* To check the status of the Ingress Controller, enter the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc -n openshift-ingress-operator get ingresscontrollers/default -o yaml
|
|
----
|
|
+
|
|
** The `Progressing` status condition indicates whether you must take further action. For example, the status condition can indicate that you need to delete the service by entering the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc -n openshift-ingress delete services/router-default
|
|
----
|
|
+
|
|
If you delete the service, the Ingress Operator recreates it as `External`.
|