[Bug] Openshift Route using passthrough doesn't work

[m1schka]

Describe the bug
In case of using the ingress/route on openshift with the passthrough mechanism, the route cannot get created, because the path is always set here

Version
v4.4.1

To Reproduce
using a grafana like this:

  ingress:
    enabled: true
    # tlsEnabled: true
    # tlsSecretName: project-ingress-cert
    targetPort: grafana-proxy
    # let the service handle the tls secret because the operator doesn't embed a tls secret into the route object
    termination: passthrough
  service:
    annotations:
      service.alpha.openshift.io/serving-cert-secret-name: project-ingress-cert

resulting in:

message: >-
    Route.route.openshift.io "grafana-route" is invalid: spec.path: Invalid
    value: "/": passthrough termination does not support paths
  phase: failing

Expected behavior
expect the route to get created/updated properly

Suspect component/Location where the bug might be occuring
here needs to be a check whether the termination is passthrough, then allow an empty path

Additional context
We use this workaround, because the ingress spec tls variables are ignored when creating a route object. We wouldn't need it if the operator would get the referenced secret from tlsSecretName and embedd it into the route object. (you can create a feature request out of this, if you like)

[NissesSenap]

Yeah sadly this sounds reasonable. @m1schka are you willing/able to create a PR to solve this issue?

[HubertStefanski]

@m1schka Can you verify that this is resolved through #773, feel free to reopen this if it still isn't resolved, thanks :thumbs4