OpenShift Route Operations: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 10: | Line 10: | ||
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]]> | ||
=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 | |||
... | |||
Revision as of 07:17, 26 November 2017
Internal
Expose a Service
Expose a service externally:
oc expose service my-service [--hostname=something.example.com]
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
...