Based on the context in the workflow application is running, the operator should expose it by default (configurable via the Platform, a user might opt out of this default behavior):

• On Minikube, it could expose the service as a NodePort: https://minikube.sigs.k8s.io/docs/handbook/accessing/
• On KIND a possibility is to use the LoadBalancer: https://kind.sigs.k8s.io/docs/user/loadbalancer/
• On Kubernetes, an ingress
• On OpenShift, a route

If this feature turns out to be too complex to implement every possibility, we can prioritize Minikube and KIND, and open a follow-up JIRA to handle Kubernetes and OpenShift.