feat(stackable-operator): Add OpenShift Route Listener service type - #1291

Knit Bundle

View bundle

This PR is part of Knit bundle openshift-route-listeners.

See the other review objects in this bundle:

• operator-rs: feat(stackable-operator): Add OpenShift Route Listener service type #1291 (this PR)
• listener-operator: feat: Add OpenShift Route support for Listeners listener-operator#435

Bundle id: openshift-route-listeners
Bundle title: Add OpenShift Route support to Listeners

Description

Part of stackabletech/listener-operator#303.

Adds an OpenShiftRoute value to the Listener ServiceType and an optional ListenerClass.spec.openshiftRoute block:

apiVersion: listeners.stackable.tech/v1alpha1
kind: ListenerClass
metadata:
  name: external-route
spec:
  serviceType: OpenShiftRoute
  openshiftRoute:
    port: https        # optional if the Listener has exactly one port
    tls: Passthrough   # default; `None` exposes plain HTTP on port 80

Only the CRD types live here. The listener-operator implementation (creating and cleaning up the Route, and publishing the hostnames OpenShift has accepted for it into Listener.status) is in stackabletech/listener-operator (linked below).

Why a serviceType

The ListenerClass already decides how a Listener is exposed. Making Route one more way of exposing it lets the product operators work unchanged, because they already read Listener.status.ingressAddresses. A separate opt-in field would duplicate that selection logic.

Breaking change

ServiceType is not #[non_exhaustive], so match statements that list every value must handle OpenShiftRoute. Within Stackable, only listener-operator matches on it. The CHANGELOG marks the change as BREAKING.

Checklist

• CRD documentation for all new fields
• Regenerated crds/ListenerClass.yaml
• Round-trip test data covers the new variants
• Changelog updated
• CRD changes approved