Generating the OpenShift Route CRD using the quarkus-maven-plugin fails when using TLS b/c is adds a path field

[johnpoth]

Describe the bug

Generating the OpenShift Route CRD using the quarkus-maven-plugin fails when using TLS. Here is the configuration:

quarkus.openshift.ports.http.tls=true
quarkus.openshift.ports.http.container-port=8443
quarkus.openshift.ports.http.host-port=8443
quarkus.openshift.route.expose=true
quarkus.openshift.route.tls.termination=passthrough
quarkus.openshift.route.tls.insecure-edge-termination-policy=Redirect

Which generates the following Route CRD:

apiVersion: route.openshift.io/v1
kind: Route
...
spec:
  path: /

Which gives the following error when deploying to OpenShift: " Message: Route.route.openshift.io "camel-http-ssl-server" is invalid: spec.path: Invalid value: "/": passthrough termination does not support paths.". Tested with latest version.

Expected behavior

No Path field in Route CRD:

apiVersion: route.openshift.io/v1
kind: Route
...
spec:

Actual behavior

Contains path element

apiVersion: route.openshift.io/v1
kind: Route
...
spec:
  path: /

How to Reproduce?

Use the following application.properties:

quarkus.openshift.ports.http.tls=true
quarkus.openshift.ports.http.container-port=8443
quarkus.openshift.ports.http.host-port=8443
quarkus.openshift.route.expose=true
quarkus.openshift.route.tls.termination=passthrough
quarkus.openshift.route.tls.insecure-edge-termination-policy=Redirect

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

Great project! Let me know if you need more info. I tested with latest platform 3.17.4. Any workaround is appreciated, thanks!

[quarkus-bot]

/cc @geoand (openshift), @iocanel (openshift), @quarkusio/devtools (maven)