OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history bug_report picture_as_pdf
×

Patching existing ingress objects

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

  • Specifications

  • Host

  • Path

  • Backend services

  • SSL/TLS settings

  • Annotations

Patching Ingress objects to resolve an ingressWithoutClassName alert

The ingressClassName field specifies the name of the IngressClass object. You must define the ingressClassName field for each Ingress object.

If you have not defined the ingressClassName field for an Ingress object, you could experience routing issues. After 24 hours, you will receive an ingressWithoutClassName alert to remind you to set the ingressClassName field.

Procedure

Patch the Ingress objects with a completed ingressClassName field to ensure proper routing and functionality.

  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:

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

    Replace <ingress_name> with the name of the Ingress object. This command patches the Ingress object to include the desired ingress class name.