Chapter 7. Use cases 165
efficient, perfect for data-intensive real-time applications that run across distributed 
devices.
    Tags: builder, nodejs, nodejs-10.16.3
    * The source repository appears to match: nodejs
    * A source build using source code from https://github.com/sclorg/nodejs-ex will be 
created
      * The resulting image will be pushed to image stream tag "nodejs-ex:latest"
      * Use 'start-build' to trigger a new build
    * This image will be deployed in deployment config "nodejs-ex"
    * Port 8080/tcp will be load balanced by service "nodejs-ex"
      * Other containers can access this service through the hostname "nodejs-ex"
--> Creating resources with label name=myapp ...
    imagestream.image.openshift.io "nodejs-ex" created
    buildconfig.build.openshift.io "nodejs-ex" created
    deploymentconfig.apps.openshift.io "nodejs-ex" created
    service "nodejs-ex" created
--> Success
    Build scheduled, use 'oc logs -f bc/nodejs-ex' to track its progress.
    Application is not exposed. You can expose services to the outside world by executing 
one or more of the commands below:
     'oc expose svc/nodejs-ex' 
    Run 'oc status' to view your app.
4. Run the oc status command to verify the status of the project, as shown in Example 7-4.
Example 7-4   Run oc status command
# oc status
In project nodejs (nodejs-example) on server https://ocp.domain.example.com:8443
svc/nodejs-ex - 172.30.186.102:8080
  dc/nodejs-ex deploys istag/nodejs-ex:latest <-
    bc/nodejs-ex source builds https://github.com/sclorg/nodejs-ex on openshift/nodejs:10 
    deployment #1 pending 6 seconds ago
3 infos identified, use 'oc status --suggest' to see details.
5. Expose the nodejs-ex service, as shown in Example 7-5.
Example 7-5   Expose nodejs-ex
# oc get svc
NAME        TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
nodejs-ex   ClusterIP   172.30.186.102   <none>        8080/TCP   7m
# oc expose svc/nodejs-ex --hostname=myapp.apps.domain.example.com
route.route.openshift.io/nodejs-ex exposed
# oc get routes
NAME        HOST/PORT PATH      SERVICES    PORT       TERMINATION   WILDCARD
nodejs-ex   myapp.apps.domain.example.com nodejs-ex   8080-tcp                 None
Note: The oc expose command supports generating only unsecured routes. For 
generating secured (edge, pass-through, re-encrypt) routes, use the oc create route 
command.