2025-01-22 09:46:07 -05:00
// Module included in the following assemblies:
//
// * networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-patch-fields.adoc
:_mod-docs-content-type: PROCEDURE
[id="nw-patch-fields-example_{context}"]
= Patching Ingress objects to resolve an ingressWithoutClassName alert
2025-12-18 15:49:51 +00:00
[role="_abstract"]
To prevent certain routing issues, you must define define the `ingressClassName` field for each `Ingress` object.
2025-01-22 09:46:07 -05:00
2025-12-18 15:49:51 +00:00
[NOTE]
====
Approximately 24 hours after you create an `Ingress` object, the Ingress Controller sends you an `ingressWithoutClassName` alert to remind you to set the `ingressClassName` field.
====
2025-01-22 09:46:07 -05:00
2025-12-18 15:49:51 +00:00
The procedure demonstrates patching the `Ingress` objects with a completed `ingressClassName` field to ensure proper routing and functionality.
2025-01-22 09:46:07 -05:00
2025-12-18 15:49:51 +00:00
.Procedure
2025-01-22 09:46:07 -05:00
. List all `IngressClass` objects:
+
[source,terminal]
----
$ oc get ingressclass
----
. List all `Ingress` objects in all namespaces:
+
[source,terminal]
----
$ oc get ingress -A
----
2025-12-18 15:49:51 +00:00
. Patch the `Ingress` object by running the following command. This command patches the `Ingress` object to include the desired ingress class name.
2025-01-22 09:46:07 -05:00
+
[source,terminal]
----
$ oc patch ingress/<ingress_name> --type=merge --patch '{"spec":{"ingressClassName":"openshift-default"}}'
----
2025-12-18 15:49:51 +00:00
* `<ingress_name>`: Replace `<ingress_name>` with the name of the `Ingress` object.