OpenShift Route Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 31: | Line 31: | ||
termination: edge | termination: edge | ||
... | ... | ||
=Unsecure Routes= | |||
<font color=red>Unsecure routes do not seem to work, investigate and write down.</font> | |||
Revision as of 21:05, 27 November 2017
Internal
Route Information
oc get route
oc edit route nexus
Expose a Service
Expose a service externally:
oc expose service <service-name> [--hostname=<fully-qualified-external-name>] [--port=<target-port>]
If --hostname is not specified, the standard <appname>-<projectname>.<default-routing-subdomain>
Specifying Termination Policy
In some cases, services were not publicly exposed because their route did not have a termination policy. To add a termination policy:
oc edit route <route-name>
and then
spec:
...
tls:
insecureEdgeTerminationPolicy: Redirect
termination: edge
...
Unsecure Routes
Unsecure routes do not seem to work, investigate and write down.