OpenShift Route Operations: Difference between revisions
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
Expose a service externally: | Expose a service externally: | ||
[[oc expose]] service | [[oc expose]] service <''service-name''> [--hostname=<''fully-qualified-external-name''>] [--port=<''target-port>''] | ||
If --hostname is not specified, the standard <appname>-<projectname>.<[[OpenShift_Concepts#Default_Routing_Subdomain|default-routing-subdomain]]> | If --hostname is not specified, the standard <appname>-<projectname>.<[[OpenShift_Concepts#Default_Routing_Subdomain|default-routing-subdomain]]> | ||
Revision as of 21:00, 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
...