This is a cache of https://docs.okd.io/4.18/networking/ingress_load_balancing/configuring_ingress_cluster_traffic/configuring-ingress-cluster-patch-fields.html. It is a snapshot of the page at 2026-01-31T22:37:32.302+0000.
Patching existing <strong>ingress</strong> objects - <strong>ingress</strong> and load balancing | Networking | OKD 4.18
  1. Documentation
×

Patching existing ingress objects

You can update or modify the following fields of existing ingress objects without recreating the objects or disrupting services to these objects:

  • Specifications

  • Host

  • Path

  • Backend services

  • SSL/TLS settings

  • Annotations

Patching ingress objects to resolve an ingressWithoutClassName alert

To prevent certain routing issues, you must define define the ingressClassName field for each ingress object.

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.

The procedure demonstrates patching the ingress objects with a completed ingressClassName field to ensure proper routing and functionality.

Procedure

  1. List all ingressClass objects:

    $ oc get ingressclass

  2. List all ingress objects in all namespaces:

    $ oc get ingress -A

  3. Patch the ingress object by running the following command. This command patches the ingress object to include the desired ingress class name.

    $ oc patch ingress/<ingress_name> --type=merge --patch '{"spec":{"ingressClassName":"openshift-default"}}'

    • <ingress_name>: Replace <ingress_name> with the name of the ingress object.