% oc explain ingresses.status.componentRoutes.currentHostnames --api-version=config.openshift.io/v1
KIND:     Ingress
VERSION:  config.openshift.io/v1

FIELD:    currentHostnames <[]string>

DESCRIPTION:
     currentHostnames is the list of current names used by the route. Typically,
     this list should consist of a single hostname, but if multiple hostnames
     are supported by the route the operator may write multiple entries to this
     list.

     Hostname is an alias for hostname string validation. The left operand of
     the | is the original kubebuilder hostname validation format, which is
     incorrect because it allows upper case letters, disallows hyphen or number
     in the TLD, and allows labels to start/end in non-alphanumeric characters.
     See https://bugzilla.redhat.com/show_bug.cgi?id=2039256.
     ^([a-zA-Z0-9\p{S}\p{L}]((-?[a-zA-Z0-9\p{S}\p{L}]{0,62})?)|([a-zA-Z0-9\p{S}\p{L}](([a-zA-Z0-9-\p{S}\p{L}]{0,61}[a-zA-Z0-9\p{S}\p{L}])?)(\.)){1,}([a-zA-Z\p{L}]){2,63})$
     The right operand of the | is a new pattern that mimics the current API
     route admission validation on hostname, except that it allows hostnames
     longer than the maximum length:
     ^(([a-z0-9][-a-z0-9]{0,61}[a-z0-9]|[a-z0-9]{1,63})[\.]){0,}([a-z0-9][-a-z0-9]{0,61}[a-z0-9]|[a-z0-9]{1,63})$
     Both operand patterns are made available so that modifications on ingress
     spec can still happen after an invalid hostname was saved via validation by
     the incorrect left operand of the | operator.

% oc explain ingresses.status.componentRoutes.currentHostnames --api-version=config.openshift.io/v1
KIND:     Ingress
VERSION:  config.openshift.io/v1

FIELD:    currentHostnames <[]string>

DESCRIPTION:
     currentHostnames is the list of current names used by the route. Typically,
     this list should consist of a single hostname, but if multiple hostnames
     are supported by the route the operator may write multiple entries to this
     list.