Customize the ingresscontroller in OSD and ROSA

Solution Verified - Updated -

Environment

  • Red Hat OpenShift Service on AWS (ROSA)
    • 4
  • Red Hat OpenShift Dedicated (OSD)
    • 4
  • Ingress Controller
  • Custom Domains Operator (CDO)

Issue

Resolution

It is currently possible to enable a feature for allowing the customization of the ingresscontroller in OSD and ROSA 4.13 clusters, and it will be the default behavior for 4.14 new installed clusters. There is additional information in Creating fully customizable non-default IngressController for ROSA (and the section "Early Access/Opting Out" for enabling it in 4.13).

For 4.13 and older versions

For 4.13 versions without the new feature enabled, and for older versions, the allowed configuration for the ingresscontroller created by the installation (default and apps2) is via OCM to made them either publicly accessible over the Internet or only privately accessible over a preexisting private connection.
Additional information at:

It is not supported:

  • Make changes to the ingresscontroller: default and apps2
  • Manually create new ingresscontroller in OSD and ROSA.

Custom Domains Operator (CDO)

In OSD and ROSA, although with limited configurations, it is possible to create a custom ingresscontroller using the Custom Domains Operator.

Recent features in CDO:

  • It is now possible to configure route sharding as explained in the CDO documentation.

Root Cause

It is currently possible to enable a feature for allowing the customization of the ingresscontroller in OSD and ROSA 4.13 clusters, and it will be the default behavior for 4.14 new installed clusters.

The configurations allowed in older releases are limited.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments