URL: https://rol.redhat.com/rol/app/courses/do180-4.12/pages/ch07s08
Reporter RHNID:
Section: 8 - Automatic Image Updates with OpenShift Image Change Triggers
Language: en-US (English)||||||||
Workaround: [student@workstation ~]$ oc expose deployment/version --name myversion --port 8080
service/myversion exposed
[student@workstation ~]$ oc expose service/myversion
route.route.openshift.io/myversion exposed
[student@workstation ~]$ oc get routes
NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD
myversion myversion-updates-triggers.apps.ocp4.example.com myversion 8080 None
[student@workstation ~]$ curl myversion-updates-triggers.apps.ocp4.example.com
Hi!

Description: The sample application "version" application deployed in updates-triggers namespace uses a service NodePort to expose.  Why? Use clusterip and route instead. 

Nodeport has some niche uses and is supported, but for the application and scenario used here it doesn't make sense. 

The lab start Use the standard way to expose the web application via a route.

`lab start updates-triggers` should expose the application via a route.