{"id":50034,"date":"2026-06-23T07:30:23","date_gmt":"2026-06-23T07:30:23","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=50034"},"modified":"2026-06-23T07:30:25","modified_gmt":"2026-06-23T07:30:25","slug":"openshift-build-your-application-from-a-container-image","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/openshift-build-your-application-from-a-container-image\/","title":{"rendered":"OpenShift Lab 12: Deploy an Application from an Existing Container Image Using the OpenShift Web Console"},"content":{"rendered":"\n

Lab Objective<\/h2>\n\n\n\n

In this lab, you will deploy an application on OpenShift from an existing container image.<\/p>\n\n\n\n

This lab is different from building an application from source code. In the previous source-code lab, OpenShift pulled code from Git and built a container image. In this lab, the container image already exists in an external container registry, so OpenShift only needs to pull the image and run it.<\/p>\n\n\n\n

By the end of this lab, you will understand how OpenShift deploys a ready-made container image using the web console.<\/p>\n\n\n\n

\n\n\n\n

What You Will Learn<\/h2>\n\n\n\n

You will learn how to:<\/p>\n\n\n\n

    \n
  1. Start OpenShift Local.<\/li>\n\n\n\n
  2. Log in to the OpenShift web console.<\/li>\n\n\n\n
  3. Create a new project.<\/li>\n\n\n\n
  4. Deploy an application from an external container image.<\/li>\n\n\n\n
  5. Use the OpenShift web console Container images<\/strong> option.<\/li>\n\n\n\n
  6. Create a Deployment.<\/li>\n\n\n\n
  7. Create a Service.<\/li>\n\n\n\n
  8. Create a Route.<\/li>\n\n\n\n
  9. Open the application in a browser.<\/li>\n\n\n\n
  10. Validate the deployment using the oc<\/code> CLI.<\/li>\n\n\n\n
  11. Inspect pods, services, routes, labels, and logs.<\/li>\n\n\n\n
  12. Scale the application.<\/li>\n\n\n\n
  13. Troubleshoot common image deployment issues.<\/li>\n\n\n\n
  14. Clean up the lab environment.<\/li>\n<\/ol>\n\n\n\n
    \n\n\n\n

    Lab Scenario<\/h2>\n\n\n\n

    You already have a container image stored in a registry.<\/p>\n\n\n\n

    You want to run that image on OpenShift without building source code.<\/p>\n\n\n\n

    For this lab, you will use the following public sample image:<\/p>\n\n\n

    quay.io\/openshiftroadshow\/parksmap:latest\n<\/code><\/span><\/pre>\n\n\n
    This image is used in Red Hat\u2019s OpenShift learning material as a sample front-end application.<\/p>\n\n\n\n
    \n\n\n\n
    Lab Architecture<\/h2>\n\n\n
    External Container Registry\n        |\n        v\nOpenShift pulls image\n        |\n        v\nDeployment\n        |\n        v\nReplicaSet\n        |\n        v\nPod\n        |\n        v\nService\n        |\n        v\nRoute\n        |\n        v\nBrowser\n<\/code><\/span><\/pre>\n\n\n
    \n\n\n\n
    Key Difference: Source Code Build vs Container Image Deployment<\/h2>\n\n\n\n
    Area<\/th>Build from Source Code<\/th>Deploy from Container Image<\/th><\/tr><\/thead>
    Input<\/td>Git repository<\/td>Existing container image<\/td><\/tr>
    Build required?<\/td>Yes<\/td>No<\/td><\/tr>
    BuildConfig created?<\/td>Yes<\/td>No<\/td><\/tr>
    ImageStream may be created?<\/td>Yes<\/td>Not always<\/td><\/tr>
    Faster?<\/td>Usually slower<\/td>Usually faster<\/td><\/tr>
    Best for<\/td>Developers building code<\/td>Teams deploying already-built images<\/td><\/tr>
    Example<\/td>Node.js app from GitHub<\/td>App image from Quay, Docker Hub, or internal registry<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    \n\n\n\n
    OpenShift Resources Created in This Lab<\/h2>\n\n\n\n
    When you deploy from a container image, OpenShift creates these resources:<\/p>\n\n\n\n
    Resource<\/th>Purpose<\/th><\/tr><\/thead>
    Project<\/td>Isolated namespace for this lab<\/td><\/tr>
    Deployment<\/td>Defines and manages the running application<\/td><\/tr>
    ReplicaSet<\/td>Maintains the desired number of pods<\/td><\/tr>
    Pod<\/td>Runs the container<\/td><\/tr>
    Service<\/td>Provides stable internal access to the pod<\/td><\/tr>
    Route<\/td>Provides browser access from outside the cluster<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    Unlike a source-code build lab, this lab does not<\/strong> create a BuildConfig or Build, because no build is needed.<\/p>\n\n\n\n
    \n\n\n\n
    Part 1: Prerequisites<\/h1>\n\n\n\n
    Required Tools<\/h2>\n\n\n\n
    You need:<\/p>\n\n\n\n
      \n
    1. OpenShift Local installed.<\/li>\n\n\n\n
    2. crc<\/code> command available.<\/li>\n\n\n\n
    3. oc<\/code> command available.<\/li>\n\n\n\n
    4. Browser access to the OpenShift web console.<\/li>\n\n\n\n
    5. Internet access from OpenShift Local to pull the container image.<\/li>\n<\/ol>\n\n\n\n
      \n\n\n\n
      Recommended Local Machine Resources<\/h2>\n\n\n\n
      Use at least:<\/p>\n\n\n\n
      Resource<\/th>Recommended<\/th><\/tr><\/thead>
      CPU<\/td>4 cores or more<\/td><\/tr>
      Memory<\/td>12 GB or more<\/td><\/tr>
      Disk<\/td>35 GB or more<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      \n\n\n\n
      Part 2: Start OpenShift Local<\/h1>\n\n\n\n
      Open a terminal.<\/p>\n\n\n\n
      Check CRC version:<\/p>\n\n\n
      crc version\n<\/code><\/span><\/pre>\n\n\n
      Set the OpenShift preset:<\/p>\n\n\n
      crc config set<\/span> preset openshift\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Run setup:<\/p>\n\n\n
      crc setup\n<\/code><\/span><\/pre>\n\n\n
      Start OpenShift Local:<\/p>\n\n\n
      crc start\n<\/code><\/span><\/pre>\n\n\n
      The startup may take several minutes.<\/p>\n\n\n\n
      To view the OpenShift Local credentials:<\/p>\n\n\n
      crc console<\/span> --credentials\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      To open the web console:<\/p>\n\n\n
      crc console<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      \n\n\n\n
      Part 3: Configure the oc<\/code> CLI<\/h1>\n\n\n\n
      Run:<\/p>\n\n\n
      crc oc-env\n<\/code><\/span><\/pre>\n\n\n
      On Linux or macOS, run:<\/p>\n\n\n
      eval<\/span> $(crc oc-env)\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      On Windows PowerShell, copy and run the command printed by crc oc-env<\/code>.<\/p>\n\n\n\n
      Log in as the developer<\/code> user:<\/p>\n\n\n
      oc login -u developer https:\/\/api.crc.testing:6443<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Use the password from:<\/p>\n\n\n
      crc console<\/span> --credentials\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Verify login:<\/p>\n\n\n
      oc whoami\n<\/code><\/span><\/pre>\n\n\n
      Expected output:<\/p>\n\n\n
      developer\n<\/code><\/span><\/pre>\n\n\n
      Check the node:<\/p>\n\n\n
      oc get<\/span> nodes\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      Expected output should show one OpenShift Local node in Ready<\/code> status.<\/p>\n\n\n\n
      \n\n\n\n
      Part 4: Create a New Project<\/h1>\n\n\n\n
      Option A: Create Project from Web Console<\/h2>\n\n\n\n
        \n
      1. Open the OpenShift web console.<\/li>\n\n\n\n
      2. Log in as developer<\/code>.<\/li>\n\n\n\n
      3. Switch to the Developer<\/strong> perspective.<\/li>\n\n\n\n
      4. Click the Project<\/strong> dropdown.<\/li>\n\n\n\n
      5. Click Create Project<\/strong>.<\/li>\n\n\n\n
      6. Enter:<\/li>\n<\/ol>\n\n\n
        lab12-container-image\n<\/code><\/span><\/pre>\n\n\n
          \n
        1. Optional display name:<\/li>\n<\/ol>\n\n\n
          Lab 12 Container Image\n<\/code><\/span><\/pre>\n\n\n
            \n
          1. Click Create<\/strong>.<\/li>\n<\/ol>\n\n\n\n
            \n\n\n\n
            Option B: Create Project from CLI<\/h2>\n\n\n\n
            Run:<\/p>\n\n\n
            oc new<\/span>-project lab12-container-image\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
            Verify:<\/p>\n\n\n
            oc project\n<\/code><\/span><\/pre>\n\n\n
            Expected output:<\/p>\n\n\n
            Using project \"lab12-container-image\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
            \n\n\n\n
            Part 5: Deploy the Application from a Container Image<\/h1>\n\n\n\n
            In the OpenShift web console:<\/p>\n\n\n\n
              \n
            1. Make sure you are in the project:<\/li>\n<\/ol>\n\n\n
              lab12-container-image\n<\/code><\/span><\/pre>\n\n\n
                \n
              1. Switch to the Developer<\/strong> perspective.<\/li>\n\n\n\n
              2. Click +Add<\/strong>.<\/li>\n\n\n\n
              3. Click Container images<\/strong>.<\/li>\n<\/ol>\n\n\n\n
                Depending on your OpenShift version, you may also see this from the quick-create +<\/code> icon.<\/p>\n\n\n\n
                \n\n\n\n
                Image Section<\/h2>\n\n\n\n
                Select:<\/p>\n\n\n
                Image name from<\/span> external registry\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                In the image name field, enter:<\/p>\n\n\n
                quay.io\/openshiftroadshow\/parksmap:latest\n<\/code><\/span><\/pre>\n\n\n
                OpenShift will validate the image.<\/p>\n\n\n\n
                If validation takes time, wait for a few seconds.<\/p>\n\n\n\n
                \n\n\n\n
                Runtime Icon<\/h2>\n\n\n\n
                For the runtime icon, you can select a suitable icon such as:<\/p>\n\n\n
                Java\n<\/code><\/span><\/pre>\n\n\n
                or keep the default detected icon.<\/p>\n\n\n\n
                The icon does not affect the deployment. It only changes how the workload appears in the Topology view.<\/p>\n\n\n\n
                \n\n\n\n
                Part 6: Configure General Settings<\/h1>\n\n\n\n
                Scroll to the General<\/strong> section.<\/p>\n\n\n\n
                Use these values:<\/p>\n\n\n\n
                Field<\/th>Value<\/th><\/tr><\/thead>
                Application name<\/td>national-parks-app<\/code><\/td><\/tr>
                Name<\/td>parksmap<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                Enter:<\/p>\n\n\n
                Application name: national-parks-app\nName: parksmap\n<\/code><\/span><\/pre>\n\n\n
                The Application name<\/strong> groups related components visually in the Topology view.<\/p>\n\n\n\n
                The Name<\/strong> is used for the actual OpenShift resources such as Deployment, Service, and Route.<\/p>\n\n\n\n
                \n\n\n\n
                Part 7: Select Resource Type<\/h1>\n\n\n\n
                In the Resource type<\/strong> section, select:<\/p>\n\n\n
                Deployment\n<\/code><\/span><\/pre>\n\n\n
                Do not select DeploymentConfig<\/code>.<\/p>\n\n\n\n
                A Deployment is the standard Kubernetes workload resource and is the best option for current beginner labs.<\/p>\n\n\n\n
                \n\n\n\n
                Part 8: Create a Route<\/h1>\n\n\n\n
                In the Advanced options<\/strong> section, make sure this is enabled:<\/p>\n\n\n
                Create a route to the application\n<\/code><\/span><\/pre>\n\n\n
                A Route is required because this is a web application and students need to open it in a browser.<\/p>\n\n\n\n
                Without a Route, the application would run inside the cluster, but it would not be accessible from your browser.<\/p>\n\n\n\n
                \n\n\n\n
                Part 9: Add Labels<\/h1>\n\n\n\n
                Click the Labels<\/strong> section.<\/p>\n\n\n\n
                Add the following labels:<\/p>\n\n\n
                app=national-parks-app\ncomponent=parksmap\nrole=frontend\n<\/code><\/span><\/pre>\n\n\n
                These labels help organize the application and make it easier to identify resources.<\/p>\n\n\n\n
                They are also useful for selectors, filtering, and the Topology view.<\/p>\n\n\n\n
                \n\n\n\n
                Part 10: Create the Application<\/h1>\n\n\n\n
                Review your configuration.<\/p>\n\n\n\n
                Setting<\/th>Expected Value<\/th><\/tr><\/thead>
                Project<\/td>lab12-container-image<\/code><\/td><\/tr>
                Image source<\/td>External registry<\/td><\/tr>
                Image<\/td>quay.io\/openshiftroadshow\/parksmap:latest<\/code><\/td><\/tr>
                Application name<\/td>national-parks-app<\/code><\/td><\/tr>
                Name<\/td>parksmap<\/code><\/td><\/tr>
                Resource type<\/td>Deployment<\/td><\/tr>
                Create route<\/td>Enabled<\/td><\/tr>
                Labels<\/td>app=national-parks-app<\/code>, component=parksmap<\/code>, role=frontend<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                Click:<\/p>\n\n\n
                Create\n<\/code><\/span><\/pre>\n\n\n
                OpenShift now creates the application.<\/p>\n\n\n\n
                Because this lab uses an existing image, there is no build step.<\/p>\n\n\n\n
                \n\n\n\n
                Part 11: Watch the Application in Topology<\/h1>\n\n\n\n
                After clicking Create<\/strong>, OpenShift redirects you to the Topology<\/strong> view.<\/p>\n\n\n\n
                You should see a workload named:<\/p>\n\n\n
                parksmap\n<\/code><\/span><\/pre>\n\n\n
                Wait until the workload shows as running.<\/p>\n\n\n\n
                Click the parksmap<\/code> workload.<\/p>\n\n\n\n
                You should see tabs or sections such as:<\/p>\n\n\n\n
                  \n
                1. Details<\/li>\n\n\n\n
                2. Resources<\/li>\n\n\n\n
                3. Observe<\/li>\n\n\n\n
                4. Logs<\/li>\n<\/ol>\n\n\n\n
                  The exact layout may vary slightly by OpenShift version.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 12: Open the Application in a Browser<\/h1>\n\n\n\n
                  In the Topology view:<\/p>\n\n\n\n
                    \n
                  1. Click the parksmap<\/code> workload.<\/li>\n\n\n\n
                  2. Click the external URL or open-route icon.<\/li>\n\n\n\n
                  3. A browser tab should open.<\/li>\n<\/ol>\n\n\n\n
                    You should see the ParksMap web application page.<\/p>\n\n\n\n
                    If the page does not load immediately, wait for the pod to become ready and refresh the browser.<\/p>\n\n\n\n
                    \n\n\n\n
                    Part 13: Validate the Deployment Using CLI<\/h1>\n\n\n\n
                    Set the project:<\/p>\n\n\n
                    oc project lab12-container-image\n<\/code><\/span><\/pre>\n\n\n
                    List all created resources:<\/p>\n\n\n
                    oc get<\/span> all\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Expected resources include:<\/p>\n\n\n
                    deployment.apps\/parksmap\nreplicaset.apps\/parksmap-xxxxx\npod\/parksmap-xxxxx\nservice\/parksmap\nroute.route.openshift.io\/parksmap\n<\/code><\/span><\/pre>\n\n\n
                    List only the important resources:<\/p>\n\n\n
                    oc get<\/span> deployment,pod,svc,route\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Expected output should show:<\/p>\n\n\n
                    deployment.apps\/parksmap\npod\/parksmap-xxxxx\nservice\/parksmap\nroute.route.openshift.io\/parksmap\n<\/code><\/span><\/pre>\n\n\n
                    \n\n\n\n
                    Part 14: Check the Deployment<\/h1>\n\n\n\n
                    Run:<\/p>\n\n\n
                    oc get<\/span> deployment parksmap\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Expected output:<\/p>\n\n\n
                    NAME       READY   UP-TO-DATE   AVAILABLE   AGE\nparksmap   1\/1     1            1           ...\n<\/code><\/span><\/pre>\n\n\n
                    Check rollout status:<\/p>\n\n\n
                    oc rollout status deployment\/parksmap\n<\/code><\/span><\/pre>\n\n\n
                    Expected output:<\/p>\n\n\n
                    deployment \"parksmap\"<\/span> successfully rolled out\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Describe the Deployment:<\/p>\n\n\n
                    oc describe deployment parksmap\n<\/code><\/span><\/pre>\n\n\n
                    Check the image used by the Deployment:<\/p>\n\n\n
                    oc get deployment parksmap -o jsonpath='{.spec.template.spec.containers[0].image}{\"\\n\"}'<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Expected output:<\/p>\n\n\n
                    quay.io\/openshiftroadshow\/parksmap:latest\n<\/code><\/span><\/pre>\n\n\n
                    \n\n\n\n
                    Part 15: Check the Pod<\/h1>\n\n\n\n
                    Run:<\/p>\n\n\n
                    oc get<\/span> pods\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Expected output:<\/p>\n\n\n
                    NAME                        READY   STATUS    RESTARTS   AGE\nparksmap-xxxxxxxxxx-xxxxx   1\/1     Running   0          ...\n<\/code><\/span><\/pre>\n\n\n
                    View pod logs:<\/p>\n\n\n
                    oc logs deployment\/parksmap\n<\/code><\/span><\/pre>\n\n\n
                    If the pod is not running, describe it:<\/p>\n\n\n
                    oc describe pod -l deployment=parksmap\n<\/code><\/span><\/pre>\n\n\n
                    If that selector does not work in your environment, list labels first:<\/p>\n\n\n
                    oc get<\/span> pods --show-labels\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Then use the correct label shown in your output.<\/p>\n\n\n\n
                    \n\n\n\n
                    Part 16: Check the Service<\/h1>\n\n\n\n
                    Run:<\/p>\n\n\n
                    oc get<\/span> svc parksmap\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Expected output:<\/p>\n\n\n
                    NAME       TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE\nparksmap   ClusterIP   ...             <none<\/span>><\/span>        8080\/TCP   ...\n<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
                    The Service provides internal cluster access to the application.<\/p>\n\n\n\n
                    Inside the same OpenShift project, other pods can reach this app using:<\/p>\n\n\n
                    http:\/\/parksmap:8080<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Describe the Service:<\/p>\n\n\n
                    oc describe svc parksmap\n<\/code><\/span><\/pre>\n\n\n
                    Check endpoints:<\/p>\n\n\n
                    oc get<\/span> endpoints parksmap\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                    The endpoint should point to the running pod IP and port.<\/p>\n\n\n\n
                    If the endpoint is empty, the Service is not matching the pod labels.<\/p>\n\n\n\n
                    \n\n\n\n
                    Part 17: Check the Route<\/h1>\n\n\n\n
                    Run:<\/p>\n\n\n
                    oc get<\/span> route parksmap\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Expected output:<\/p>\n\n\n
                    NAME       HOST\/PORT                                             SERVICES   PORT\nparksmap   parksmap-lab12-container-image.apps-crc.testing       parksmap   8080\n<\/code><\/span><\/pre>\n\n\n
                    The exact hostname may be different.<\/p>\n\n\n\n
                    Store the app URL:<\/p>\n\n\n
                    APP_URL=\"http:\/\/$(oc get route parksmap -o jsonpath='{.spec.host}')\"<\/span>\necho<\/span> \"$APP_URL\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Test the route:<\/p>\n\n\n
                    curl -I \"$APP_URL\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Expected result:<\/p>\n\n\n
                    HTTP\/1.1 200<\/span> OK\n<\/code><\/span>Code language:<\/span> HTTP<\/span> (<\/span>http<\/span>)<\/span><\/small><\/pre>\n\n\n
                    A different successful HTTP response is also acceptable, depending on the image behavior.<\/p>\n\n\n\n
                    \n\n\n\n
                    Part 18: Confirm That No Build Was Created<\/h1>\n\n\n\n
                    This lab deploys an existing image. It does not build a new image.<\/p>\n\n\n\n
                    Check BuildConfigs:<\/p>\n\n\n
                    oc get<\/span> buildconfig\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Expected output:<\/p>\n\n\n
                    No resources found in lab12-container-image namespace<\/span>.\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Check Builds:<\/p>\n\n\n
                    oc get<\/span> builds\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Expected output:<\/p>\n\n\n
                    No resources found in lab12-container-image namespace<\/span>.\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                    This is correct.<\/p>\n\n\n\n
                    No BuildConfig is needed because the container image already exists.<\/p>\n\n\n\n
                    \n\n\n\n
                    Part 19: Scale the Application<\/h1>\n\n\n\n
                    You can scale the Deployment from the web console or CLI.<\/p>\n\n\n\n
                    Option A: Scale from Web Console<\/h2>\n\n\n\n
                      \n
                    1. Go to Developer<\/strong> perspective.<\/li>\n\n\n\n
                    2. Open Topology<\/strong>.<\/li>\n\n\n\n
                    3. Click the parksmap<\/code> workload.<\/li>\n\n\n\n
                    4. Open the Details<\/strong> tab.<\/li>\n\n\n\n
                    5. Increase the pod count from 1<\/code> to 2<\/code>.<\/li>\n<\/ol>\n\n\n\n
                      Wait until two pods are running.<\/p>\n\n\n\n
                      \n\n\n\n
                      Option B: Scale from CLI<\/h2>\n\n\n\n
                      Run:<\/p>\n\n\n
                      oc scale deployment\/parksmap --replicas=2\n<\/code><\/span><\/pre>\n\n\n
                      Check pods:<\/p>\n\n\n
                      oc get<\/span> pods\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                      Expected result:<\/p>\n\n\n
                      Two parksmap pods should be running.\n<\/code><\/span><\/pre>\n\n\n
                      Check Deployment:<\/p>\n\n\n
                      oc get<\/span> deployment parksmap\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                      Expected output:<\/p>\n\n\n
                      READY   2\/2\n<\/code><\/span><\/pre>\n\n\n
                      Scale back to one pod:<\/p>\n\n\n
                      oc scale deployment\/parksmap --replicas=1\n<\/code><\/span><\/pre>\n\n\n
                      Verify:<\/p>\n\n\n
                      oc get<\/span> deployment parksmap\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                      Expected output:<\/p>\n\n\n
                      READY   1\/1\n<\/code><\/span><\/pre>\n\n\n
                      \n\n\n\n
                      Part 20: Update the Container Image Tag<\/h1>\n\n\n\n
                      In real projects, teams often deploy a new application version by changing the image tag.<\/p>\n\n\n\n
                      For this beginner lab, do not change the image unless your instructor provides a tested tag.<\/p>\n\n\n\n
                      You can view the current image:<\/p>\n\n\n
                      oc get deployment parksmap -o jsonpath='{.spec.template.spec.containers[0].image}{\"\\n\"}'<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                      Example output:<\/p>\n\n\n
                      quay.io\/openshiftroadshow\/parksmap:latest\n<\/code><\/span><\/pre>\n\n\n
                      If you had another valid image tag, the update command would look like this:<\/p>\n\n\n
                      oc set image deployment\/parksmap parksmap=quay.io\/openshiftroadshow\/parksmap:<new-tag<\/span>><\/span>\n<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
                      Then check rollout:<\/p>\n\n\n
                      oc rollout status deployment\/parksmap\n<\/code><\/span><\/pre>\n\n\n
                      For this lab, keep the original image.<\/p>\n\n\n\n
                      \n\n\n\n
                      Part 21: Roll Out Restart<\/h1>\n\n\n\n
                      You can restart the application without changing the image.<\/p>\n\n\n\n
                      Run:<\/p>\n\n\n
                      oc rollout restart deployment\/parksmap\n<\/code><\/span><\/pre>\n\n\n
                      Watch rollout:<\/p>\n\n\n
                      oc rollout status deployment\/parksmap\n<\/code><\/span><\/pre>\n\n\n
                      Check pods:<\/p>\n\n\n
                      oc get<\/span> pods\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                      You should see a new pod replacing the old pod.<\/p>\n\n\n\n
                      \n\n\n\n
                      Part 22: Student Checkpoint<\/h1>\n\n\n\n
                      Students should be able to answer:<\/p>\n\n\n\n
                      Question<\/th>Expected Answer<\/th><\/tr><\/thead>
                      Did OpenShift build the image in this lab?<\/td>No<\/td><\/tr>
                      Where did the image come from?<\/td>External container registry<\/td><\/tr>
                      Which image did we use?<\/td>quay.io\/openshiftroadshow\/parksmap:latest<\/code><\/td><\/tr>
                      Which resource runs the app?<\/td>Deployment<\/td><\/tr>
                      Which resource creates the pod?<\/td>Deployment through ReplicaSet<\/td><\/tr>
                      Which resource gives internal access?<\/td>Service<\/td><\/tr>
                      Which resource gives browser access?<\/td>Route<\/td><\/tr>
                      Why was no BuildConfig created?<\/td>Because no source build was needed<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                      \n\n\n\n
                      Part 23: Full Validation Script<\/h1>\n\n\n\n
                      Run this after completing the lab:<\/p>\n\n\n
                      oc project lab12-container-image\n\necho<\/span> \"Checking Deployment...\"<\/span>\noc get deployment parksmap\n\necho<\/span> \"Checking rollout...\"<\/span>\noc rollout status deployment\/parksmap\n\necho<\/span> \"Checking pods...\"<\/span>\noc get pods -o wide\n\necho<\/span> \"Checking image...\"<\/span>\noc get deployment parksmap -o jsonpath='{.spec.template.spec.containers[0].image}{\"\\n\"}'<\/span>\n\necho<\/span> \"Checking service...\"<\/span>\noc get svc parksmap\n\necho<\/span> \"Checking endpoints...\"<\/span>\noc get endpoints parksmap\n\necho<\/span> \"Checking route...\"<\/span>\noc get route parksmap\n\necho<\/span> \"Checking that no build exists...\"<\/span>\noc get bc\noc get builds\n\necho<\/span> \"Testing application route...\"<\/span>\nAPP_URL=\"http:\/\/$(oc get route parksmap -o jsonpath='{.spec.host}')\"<\/span>\necho<\/span> \"$APP_URL\"<\/span>\ncurl -I \"$APP_URL\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                      Expected result:<\/p>\n\n\n\n
                        \n
                      1. Deployment is available.<\/li>\n\n\n\n
                      2. Pod is running.<\/li>\n\n\n\n
                      3. Service exists.<\/li>\n\n\n\n
                      4. Endpoint exists.<\/li>\n\n\n\n
                      5. Route exists.<\/li>\n\n\n\n
                      6. No BuildConfig exists.<\/li>\n\n\n\n
                      7. No Build exists.<\/li>\n\n\n\n
                      8. Browser URL works.<\/li>\n<\/ol>\n\n\n\n
                        \n\n\n\n
                        Part 24: Troubleshooting<\/h1>\n\n\n\n
                        Problem 1: ImagePullBackOff<\/h2>\n\n\n\n
                        Symptom<\/h3>\n\n\n\n
                        The pod is not running and shows:<\/p>\n\n\n
                        ImagePullBackOff\n<\/code><\/span><\/pre>\n\n\n
                        or:<\/p>\n\n\n
                        ErrImagePull\n<\/code><\/span><\/pre>\n\n\n
                        Check<\/h3>\n\n\n\n
                        Run:<\/p>\n\n\n
                        oc get<\/span> pods\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                        Describe the pod:<\/p>\n\n\n
                        oc describe pod -l app=parksmap\n<\/code><\/span><\/pre>\n\n\n
                        If that selector does not work, run:<\/p>\n\n\n
                        oc get<\/span> pods --show-labels\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                        Then describe the pod by name:<\/p>\n\n\n
                        oc describe pod <pod-name<\/span>><\/span>\n<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
                        Common Causes<\/h3>\n\n\n\n
                          \n
                        1. Wrong image name.<\/li>\n\n\n\n
                        2. Registry is temporarily unavailable.<\/li>\n\n\n\n
                        3. OpenShift Local cannot reach the registry.<\/li>\n\n\n\n
                        4. Image is private and needs a pull secret.<\/li>\n\n\n\n
                        5. VPN or firewall is blocking registry access.<\/li>\n<\/ol>\n\n\n\n
                          Fix<\/h3>\n\n\n\n
                          Verify the image name:<\/p>\n\n\n
                          quay.io\/openshiftroadshow\/parksmap:latest\n<\/code><\/span><\/pre>\n\n\n
                          Check CRC status:<\/p>\n\n\n
                          crc status\n<\/code><\/span><\/pre>\n\n\n
                          If using VPN, disconnect VPN and retry if possible.<\/p>\n\n\n\n
                          Restart the rollout:<\/p>\n\n\n
                          oc rollout restart deployment\/parksmap\n<\/code><\/span><\/pre>\n\n\n
                          \n\n\n\n
                          Problem 2: Route Does Not Open<\/h2>\n\n\n\n
                          Symptom<\/h3>\n\n\n\n
                          The pod is running, but the browser page does not open.<\/p>\n\n\n\n
                          Check<\/h3>\n\n\n\n
                          Run:<\/p>\n\n\n
                          oc get<\/span> route parksmap\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                          Check service:<\/p>\n\n\n
                          oc get<\/span> svc parksmap\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                          Check endpoints:<\/p>\n\n\n
                          oc get<\/span> endpoints parksmap\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                          If endpoints are empty, the Service is not pointing to the pod.<\/p>\n\n\n\n
                          Check pod labels:<\/p>\n\n\n
                          oc get<\/span> pods --show-labels\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                          Check Service selector:<\/p>\n\n\n
                          oc describe svc parksmap\n<\/code><\/span><\/pre>\n\n\n
                          The Service selector must match the pod labels.<\/p>\n\n\n\n
                          \n\n\n\n
                          Problem 3: Pod Is Running but App Is Not Responding<\/h2>\n\n\n\n
                          Check logs:<\/p>\n\n\n
                          oc logs deployment\/parksmap\n<\/code><\/span><\/pre>\n\n\n
                          Check pod status:<\/p>\n\n\n
                          oc describe deployment parksmap\n<\/code><\/span><\/pre>\n\n\n
                          Check whether the Service has endpoints:<\/p>\n\n\n
                          oc get<\/span> endpoints parksmap\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                          If the application listens on a different port than the Service expects, the route may fail.<\/p>\n\n\n\n
                          For this lab, the parksmap<\/code> image is expected to expose the application through port 8080<\/code>.<\/p>\n\n\n\n
                          \n\n\n\n
                          Problem 4: No Route Was Created<\/h2>\n\n\n\n
                          If you forgot to enable Create a route<\/strong>, create the Route manually:<\/p>\n\n\n
                          oc expose svc\/parksmap\n<\/code><\/span><\/pre>\n\n\n
                          Verify:<\/p>\n\n\n
                          oc get<\/span> route parksmap\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                          Open the route again.<\/p>\n\n\n\n
                          \n\n\n\n
                          Problem 5: BuildConfig Not Found<\/h2>\n\n\n\n
                          This is not an error.<\/p>\n\n\n\n
                          This lab deploys an existing image.<\/p>\n\n\n\n
                          So this output is expected:<\/p>\n\n\n
                          oc get<\/span> bc\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                          Expected:<\/p>\n\n\n
                          No resources found\n<\/code><\/span><\/pre>\n\n\n
                          A BuildConfig is only needed when OpenShift builds an image from source code or binary input.<\/p>\n\n\n\n
                          \n\n\n\n
                          Problem 6: Application Works in Browser but curl<\/code> Fails<\/h2>\n\n\n\n
                          Possible causes:<\/p>\n\n\n\n
                            \n
                          1. Local DNS issue.<\/li>\n\n\n\n
                          2. Browser has a working DNS\/proxy setup but terminal does not.<\/li>\n\n\n\n
                          3. VPN or firewall issue.<\/li>\n\n\n\n
                          4. CRC networking issue.<\/li>\n<\/ol>\n\n\n\n
                            Check CRC:<\/p>\n\n\n
                            crc status\n<\/code><\/span><\/pre>\n\n\n
                            Print the route:<\/p>\n\n\n
                            oc get<\/span> route parksmap\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Try again after a minute.<\/p>\n\n\n\n
                            \n\n\n\n
                            Part 25: Optional CLI-Only Equivalent<\/h1>\n\n\n\n
                            The main purpose of this lab is to use the web console.<\/p>\n\n\n\n
                            However, the equivalent CLI workflow is useful to know.<\/p>\n\n\n\n
                            Create a new project:<\/p>\n\n\n
                            oc new<\/span>-project lab12-container-image-cli\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Create the application from image:<\/p>\n\n\n
                            oc new<\/span>-app quay.io\/openshiftroadshow\/parksmap:latest --name=parksmap\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Expose the Service:<\/p>\n\n\n
                            oc expose svc\/parksmap\n<\/code><\/span><\/pre>\n\n\n
                            Check resources:<\/p>\n\n\n
                            oc get<\/span> deployment,pod,svc,route\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Test the route:<\/p>\n\n\n
                            APP_URL=\"http:\/\/$(oc get route parksmap -o jsonpath='{.spec.host}')\"<\/span>\ncurl -I \"$APP_URL\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Clean up the CLI test project:<\/p>\n\n\n
                            oc delete<\/span> project lab12-container-image-cli\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            \n\n\n\n
                            Part 26: Cleanup<\/h1>\n\n\n\n
                            Cleanup from Web Console<\/h2>\n\n\n\n
                              \n
                            1. Go to the Developer<\/strong> perspective.<\/li>\n\n\n\n
                            2. Select project:<\/li>\n<\/ol>\n\n\n
                              lab12-container-image\n<\/code><\/span><\/pre>\n\n\n
                                \n
                              1. Go to Topology<\/strong>.<\/li>\n\n\n\n
                              2. Open the action menu for the parksmap<\/code> application.<\/li>\n\n\n\n
                              3. Click Delete Application<\/strong>.<\/li>\n\n\n\n
                              4. Confirm deletion.<\/li>\n<\/ol>\n\n\n\n
                                This deletes the application resources.<\/p>\n\n\n\n
                                \n\n\n\n
                                Cleanup from CLI<\/h2>\n\n\n\n
                                The easiest cleanup is to delete the whole project:<\/p>\n\n\n
                                oc delete<\/span> project lab12-container-image\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                Verify:<\/p>\n\n\n
                                oc get<\/span> project lab12-container-image\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                Expected output:<\/p>\n\n\n
                                Error<\/span> from<\/span> server (NotFound): projects.project.openshift.io \"lab12-container-image\"<\/span> not found\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                \n\n\n\n
                                Part 27: Lab Summary<\/h1>\n\n\n\n
                                In this lab, you deployed an application from an existing container image using the OpenShift web console.<\/p>\n\n\n\n
                                You learned that:<\/p>\n\n\n\n
                                  \n
                                1. Container images can be deployed directly without building source code.<\/li>\n\n\n\n
                                2. The Container images<\/strong> option is used when an image already exists in a registry.<\/li>\n\n\n\n
                                3. A Deployment runs the application.<\/li>\n\n\n\n
                                4. A Pod runs the actual container.<\/li>\n\n\n\n
                                5. A Service provides internal access.<\/li>\n\n\n\n
                                6. A Route provides external browser access.<\/li>\n\n\n\n
                                7. No BuildConfig or Build is created when deploying an existing image.<\/li>\n\n\n\n
                                8. OpenShift can scale and restart the application using Deployment features.<\/li>\n<\/ol>\n\n\n\n
                                  \n\n\n\n
                                  Part 28: Review Questions<\/h1>\n\n\n\n
                                  Question 1<\/h2>\n\n\n\n
                                  What was the input for this lab?<\/p>\n\n\n\n
                                  Answer<\/h3>\n\n\n\n
                                  An existing container image:<\/p>\n\n\n
                                  quay.io\/openshiftroadshow\/parksmap:latest\n<\/code><\/span><\/pre>\n\n\n
                                  \n\n\n\n
                                  Question 2<\/h2>\n\n\n\n
                                  Did OpenShift build a new image in this lab?<\/p>\n\n\n\n
                                  Answer<\/h3>\n\n\n\n
                                  No. OpenShift pulled and ran an existing image.<\/p>\n\n\n\n
                                  \n\n\n\n
                                  Question 3<\/h2>\n\n\n\n
                                  Which OpenShift web-console option did we use?<\/p>\n\n\n\n
                                  Answer<\/h3>\n\n\n
                                  +Add -> Container images\n<\/code><\/span><\/pre>\n\n\n
                                  \n\n\n\n
                                  Question 4<\/h2>\n\n\n\n
                                  Which resource runs the application?<\/p>\n\n\n\n
                                  Answer<\/h3>\n\n\n\n
                                  Deployment.<\/p>\n\n\n\n
                                  \n\n\n\n
                                  Question 5<\/h2>\n\n\n\n
                                  Which resource exposes the application inside the cluster?<\/p>\n\n\n\n
                                  Answer<\/h3>\n\n\n\n
                                  Service.<\/p>\n\n\n\n
                                  \n\n\n\n
                                  Question 6<\/h2>\n\n\n\n
                                  Which resource exposes the application outside the cluster?<\/p>\n\n\n\n
                                  Answer<\/h3>\n\n\n\n
                                  Route.<\/p>\n\n\n\n
                                  \n\n\n\n
                                  Question 7<\/h2>\n\n\n\n
                                  Why was no BuildConfig created?<\/p>\n\n\n\n
                                  Answer<\/h3>\n\n\n\n
                                  Because OpenShift did not build source code. It deployed an image that already existed.<\/p>\n\n\n\n
                                  \n\n\n\n
                                  Question 8<\/h2>\n\n\n\n
                                  What command checks the Deployment status?<\/p>\n\n\n\n
                                  Answer<\/h3>\n\n\n
                                  oc rollout status deployment\/parksmap\n<\/code><\/span><\/pre>\n\n\n
                                  \n\n\n\n
                                  Question 9<\/h2>\n\n\n\n
                                  What command shows the Route?<\/p>\n\n\n\n
                                  Answer<\/h3>\n\n\n
                                  oc get<\/span> route parksmap\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                  \n\n\n\n
                                  Question 10<\/h2>\n\n\n\n
                                  What command deletes the full lab project?<\/p>\n\n\n\n
                                  Answer<\/h3>\n\n\n
                                  oc delete<\/span> project lab12-container-image\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                  \n\n\n\n
                                  Instructor Notes<\/h1>\n\n\n\n
                                  This lab is designed as a replacement for the older short article about deploying an application from a container image.<\/p>\n\n\n\n
                                  The old article\u2019s topic is correct, but the replacement lab improves it by:<\/p>\n\n\n\n
                                    \n
                                  1. Using OpenShift Local instead of Developer Sandbox.<\/li>\n\n\n\n
                                  2. Using an official OpenShift sample image.<\/li>\n\n\n\n
                                  3. Separating this lab from the Git\/source-code workflow.<\/li>\n\n\n\n
                                  4. Using Deployment instead of DeploymentConfig.<\/li>\n\n\n\n
                                  5. Adding route, service, pod, and deployment validation.<\/li>\n\n\n\n
                                  6. Explaining why no BuildConfig is created.<\/li>\n\n\n\n
                                  7. Adding CLI checks.<\/li>\n\n\n\n
                                  8. Adding troubleshooting.<\/li>\n\n\n\n
                                  9. Adding cleanup steps.<\/li>\n<\/ol>\n\n\n\n
                                    For production or advanced courses, add follow-up labs for:<\/p>\n\n\n\n
                                      \n
                                    1. Deploying images from a private registry.<\/li>\n\n\n\n
                                    2. Creating image pull secrets.<\/li>\n\n\n\n
                                    3. Deploying from an internal OpenShift ImageStream.<\/li>\n\n\n\n
                                    4. Updating images by tag and digest.<\/li>\n\n\n\n
                                    5. Using immutable image digests instead of latest<\/code>.<\/li>\n\n\n\n
                                    6. Image vulnerability scanning.<\/li>\n\n\n\n
                                    7. Image signing and verification.<\/li>\n\n\n\n
                                    8. GitOps-based image deployment.<\/li>\n\n\n\n
                                    9. Rollback and rollout history.<\/li>\n\n\n\n
                                    10. Resource requests and limits.<\/li>\n<\/ol>\n\n\n\n
                                      \n\n\n\n
                                      Instructor Pre-Validation Checklist<\/h1>\n\n\n\n
                                      Before delivering this lab to students, run:<\/p>\n\n\n
                                      crc status\noc whoami\noc get<\/span> nodes\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                      Create a quick test project:<\/p>\n\n\n
                                      oc new<\/span>-project lab12-test\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                      Deploy the sample image:<\/p>\n\n\n
                                      oc new<\/span>-app quay.io\/openshiftroadshow\/parksmap:latest --name=parksmap\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                      Expose it:<\/p>\n\n\n
                                      oc expose svc\/parksmap\n<\/code><\/span><\/pre>\n\n\n
                                      Validate:<\/p>\n\n\n
                                      oc rollout status deployment\/parksmap\noc get pod,svc,route\nAPP_URL=\"http:\/\/$(oc get route parksmap -o jsonpath='{.spec.host}')\"<\/span>\ncurl -I \"$APP_URL\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                                      Clean up:<\/p>\n\n\n
                                      oc delete<\/span> project lab12-test\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                      If these commands pass, the lab is ready for students.<\/p>\n\n\n\n
                                      \n\n\n\n
                                      Final Outcome<\/h1>\n\n\n\n
                                      You have successfully deployed an application from an existing container image using the OpenShift web console.<\/p>\n\n\n\n
                                      You now understand this workflow:<\/p>\n\n\n
                                      Container Image\n  -> Deployment\n  -> Pod\n  -> Service\n  -> Route\n  -> Browser\n<\/code><\/span><\/pre>\n\n\n
                                      This is one of the most common real-world OpenShift workflows because many teams build images in CI\/CD pipelines and then deploy those already-built images into OpenShift.<\/p>\n","protected":false},"excerpt":{"rendered":"
                                      Lab Objective In this lab, you will deploy an application on OpenShift from an existing container image. This lab is different from building an application from source… <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[5153],"tags":[],"class_list":["post-50034","post","type-post","status-publish","format-standard","hentry","category-openshift"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/50034","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=50034"}],"version-history":[{"count":4,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/50034\/revisions"}],"predecessor-version":[{"id":77170,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/50034\/revisions\/77170"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=50034"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=50034"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=50034"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}