{"id":50032,"date":"2026-06-23T07:20:44","date_gmt":"2026-06-23T07:20:44","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=50032"},"modified":"2026-06-23T07:20:47","modified_gmt":"2026-06-23T07:20:47","slug":"openshift-build-your-application-from-source-code","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/openshift-build-your-application-from-source-code\/","title":{"rendered":"OpenShift Lab 11: Build and Deploy an Application from Source Code Using the OpenShift Web Console"},"content":{"rendered":"\n

<\/p>\n\n\n\n

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

In this lab, you will build and deploy a web application from source code stored in a Git repository using the OpenShift web console.<\/p>\n\n\n\n

You will use OpenShift Local, also known as CRC, as the local OpenShift environment.<\/p>\n\n\n\n

This lab replaces the older Developer Sandbox-based lab and updates the steps for a local OpenShift learning environment.<\/p>\n\n\n\n

By the end of this lab, you will understand how OpenShift takes application source code from Git, builds a container image using Source-to-Image, deploys the application, creates a Service, creates a Route, and makes the application accessible from a browser.<\/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 OpenShift project.<\/li>\n\n\n\n
  4. Import application source code from a Git repository.<\/li>\n\n\n\n
  5. Use OpenShift Source-to-Image, also called S2I.<\/li>\n\n\n\n
  6. Build a container image from application source code.<\/li>\n\n\n\n
  7. Deploy the built image as a Kubernetes Deployment.<\/li>\n\n\n\n
  8. Expose the application internally using a Service.<\/li>\n\n\n\n
  9. Expose the application externally using a Route.<\/li>\n\n\n\n
  10. View the application in a browser.<\/li>\n\n\n\n
  11. Inspect BuildConfig, Build, ImageStream, Deployment, Pod, Service, and Route resources.<\/li>\n\n\n\n
  12. View build logs and pod logs.<\/li>\n\n\n\n
  13. Trigger a rebuild manually.<\/li>\n\n\n\n
  14. Troubleshoot common build and deployment issues.<\/li>\n\n\n\n
  15. Clean up the lab environment.<\/li>\n<\/ol>\n\n\n\n
    \n\n\n\n

    Lab Architecture<\/h2>\n\n\n\n

    The lab follows this flow:<\/p>\n\n\n

    Git Repository\n     |\n     v\nOpenShift Import from<\/span> Git\n     |\n     v\nSource-to-Image Build\n     |\n     v\nBuildConfig\n     |\n     v\nBuild Pod\n     |\n     v\nImageStream\n     |\n     v\nDeployment\n     |\n     v\nPod\n     |\n     v\nService\n     |\n     v\nRoute\n     |\n     v\nBrowser\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
    \n\n\n\n
    OpenShift Resources Created in This Lab<\/h2>\n\n\n\n
    When you import the application from Git, OpenShift creates several resources automatically.<\/p>\n\n\n\n
    Resource<\/th>Purpose<\/th><\/tr><\/thead>
    Project<\/td>Isolates the lab resources<\/td><\/tr>
    BuildConfig<\/td>Defines how the source code will be built<\/td><\/tr>
    Build<\/td>Represents one build execution<\/td><\/tr>
    ImageStream<\/td>Tracks the built application image inside OpenShift<\/td><\/tr>
    Deployment<\/td>Runs the application as pods<\/td><\/tr>
    ReplicaSet<\/td>Maintains the desired number of pods for the Deployment<\/td><\/tr>
    Pod<\/td>Runs the application container<\/td><\/tr>
    Service<\/td>Provides stable internal access to the pod<\/td><\/tr>
    Route<\/td>Provides browser access to the application from outside the cluster<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    \n\n\n\n
    Important Concept: What Is Source-to-Image?<\/h2>\n\n\n\n
    Source-to-Image, usually called S2I, is an OpenShift build strategy.<\/p>\n\n\n\n
    With S2I, you provide source code from Git. OpenShift combines that source code with a builder image, such as a Node.js builder image, and creates a runnable container image.<\/p>\n\n\n\n
    In simple words:<\/p>\n\n\n
    Source Code + Builder Image = Runnable Application Image\n<\/code><\/span><\/pre>\n\n\n
    For this lab:<\/p>\n\n\n
    Node.js source code + Node.js S2I builder image = Node.js application container image\n<\/code><\/span><\/pre>\n\n\n
    \n\n\n\n
    Important Concept: Why Use Deployment Instead of DeploymentConfig?<\/h2>\n\n\n\n
    Older OpenShift tutorials often used DeploymentConfig<\/code>.<\/p>\n\n\n\n
    For current beginner labs, use Deployment<\/code>.<\/p>\n\n\n\n
    A Deployment<\/code> is the standard Kubernetes workload resource. It is easier for students to understand because it matches Kubernetes concepts directly.<\/p>\n\n\n\n
    In this lab, select:<\/p>\n\n\n
    Resource type: Deployment\n<\/code><\/span><\/pre>\n\n\n
    Do not select:<\/p>\n\n\n
    DeploymentConfig\n<\/code><\/span><\/pre>\n\n\n
    \n\n\n\n
    Lab Environment<\/h2>\n\n\n\n
    This lab is written for:<\/p>\n\n\n
    OpenShift Local \/ CRC\nOpenShift Container Platform 4.<\/span>x\nDeveloper user\nOpenShift web console<\/span>\noc CLI\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
    The exact OpenShift version may vary depending on the OpenShift Local version installed on your machine.<\/p>\n\n\n\n
    \n\n\n\n
    Part 1: Prerequisites<\/h1>\n\n\n\n
    Required Software<\/h2>\n\n\n\n
    You need:<\/p>\n\n\n\n
      \n
    1. OpenShift Local installed.<\/li>\n\n\n\n
    2. The crc<\/code> command available.<\/li>\n\n\n\n
    3. The oc<\/code> command available.<\/li>\n\n\n\n
    4. A browser.<\/li>\n\n\n\n
    5. Internet access from the OpenShift Local VM to GitHub and container registries.<\/li>\n<\/ol>\n\n\n\n
      \n\n\n\n
      Recommended Machine Resources<\/h2>\n\n\n\n
      For a smooth student lab, 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
      If your laptop has limited resources, builds may take longer.<\/p>\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 the CRC version:<\/p>\n\n\n
      crc version\n<\/code><\/span><\/pre>\n\n\n
      Set CRC to use 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 can take several minutes.<\/p>\n\n\n\n
      When the cluster starts, CRC prints the web console URL and login credentials.<\/p>\n\n\n\n
      To view the credentials again, run:<\/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, run:<\/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, apply the printed command:<\/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, use the command printed by crc oc-env<\/code> for PowerShell.<\/p>\n\n\n\n
      Now log in as the developer<\/code> user.<\/p>\n\n\n\n
      Get the password:<\/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
      Login command:<\/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
      Enter the developer password when prompted.<\/p>\n\n\n\n
      Verify the 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 will look similar to this:<\/p>\n\n\n
      NAME<\/span>                 STATUS<\/span>   ROLES<\/span>                         AGE<\/span>   VERSION<\/span>\ncrc-xxxxx-master-0<\/span>   Ready<\/span>    control-plane<\/span>,master<\/span>,worker<\/span>    ...   v1<\/span>.xx<\/span>.x<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
      The exact node name and version will be different in your environment.<\/p>\n\n\n\n
      \n\n\n\n
      Part 4: Create a New Project<\/h1>\n\n\n\n
      You can create the project from the web console or from the CLI.<\/p>\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:<\/li>\n<\/ol>\n\n\n
        Username: developer\nPassword<\/span>: Use the password from<\/span> crc console<\/span> --credentials\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
          \n
        1. Switch to the Developer<\/strong> perspective.<\/li>\n\n\n\n
        2. Click the Project<\/strong> dropdown.<\/li>\n\n\n\n
        3. Click Create Project<\/strong>.<\/li>\n\n\n\n
        4. Enter the project name:<\/li>\n<\/ol>\n\n\n
          lab11-source-build\n<\/code><\/span><\/pre>\n\n\n
            \n
          1. Optional display name:<\/li>\n<\/ol>\n\n\n
            Lab 11 Source Build\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 lab11-source-build\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
              Expected output:<\/p>\n\n\n
              Now using project \"lab11-source-build\"<\/span> on server \"https:\/\/api.crc.testing:6443\"<\/span>.\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 \"lab11-source-build\"<\/span> on server \"https:\/\/api.crc.testing:6443\"<\/span>.\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
              \n\n\n\n
              Part 5: Import the Application from Git Using the Web Console<\/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
                lab11-source-build\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. Under Git Repository<\/strong>, click From Git<\/strong> or Import from Git<\/strong>.<\/li>\n<\/ol>\n\n\n\n
                  Depending on your OpenShift version, the label may appear as either:<\/p>\n\n\n
                  From Git\n<\/code><\/span><\/pre>\n\n\n
                  or:<\/p>\n\n\n
                  Import from<\/span> Git\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Both refer to the same workflow.<\/p>\n\n\n\n
                  \n\n\n\n
                  Git Repository URL<\/h2>\n\n\n\n
                  In the Git repository URL field, enter:<\/p>\n\n\n
                  https:\/\/github.com\/redhat-developer-demos\/sandbox-nodejs.git<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  This is a simple Node.js application used for OpenShift S2I demonstration.<\/p>\n\n\n\n
                  After entering the URL, OpenShift validates the repository.<\/p>\n\n\n\n
                  \n\n\n\n
                  Git Options<\/h2>\n\n\n\n
                  For this beginner lab, keep the default Git options.<\/p>\n\n\n\n
                  Field<\/th>Value<\/th><\/tr><\/thead>
                  Git Repo URL<\/td>https:\/\/github.com\/redhat-developer-demos\/sandbox-nodejs.git<\/code><\/td><\/tr>
                  Git Reference<\/td>Leave blank<\/td><\/tr>
                  Context Dir<\/td>Leave blank<\/td><\/tr>
                  Source Secret<\/td>Leave blank<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                  Use Git Reference<\/strong> only when you want to build from a specific branch, tag, or commit.<\/p>\n\n\n\n
                  Use Context Dir<\/strong> only when the application is inside a subdirectory of the Git repository.<\/p>\n\n\n\n
                  Use Source Secret<\/strong> only when the Git repository is private.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 6: Select the Import Strategy<\/h1>\n\n\n\n
                  After the Git URL is validated, OpenShift tries to detect the correct build strategy.<\/p>\n\n\n\n
                  For this lab, use:<\/p>\n\n\n
                  Import Strategy: Builder Image\n<\/code><\/span><\/pre>\n\n\n
                  OpenShift should detect that the application is a Node.js application.<\/p>\n\n\n\n
                  If it does not detect it automatically, select:<\/p>\n\n\n
                  Builder<\/span> Image<\/span>: Node<\/span>.js<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Use the latest available Node.js builder image version shown in your OpenShift web console.<\/p>\n\n\n\n
                  The exact Node.js version available depends on your OpenShift Local version and sample image configuration.<\/p>\n\n\n\n
                  For example, you might see versions such as:<\/p>\n\n\n
                  Node<\/span>.js<\/span> 18\nNode<\/span>.js<\/span> 20\nNode<\/span>.js<\/span> 22\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Select the latest available stable version.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 7: Configure Application Details<\/h1>\n\n\n\n
                  Scroll down to the application configuration section.<\/p>\n\n\n\n
                  Use the following values:<\/p>\n\n\n\n
                  Field<\/th>Value<\/th><\/tr><\/thead>
                  Application Name<\/td>lab11-source-build<\/code><\/td><\/tr>
                  Name<\/td>sandbox-nodejs<\/code><\/td><\/tr>
                  Runtime Icon<\/td>Node.js<\/td><\/tr>
                  Builder Image<\/td>Node.js<\/td><\/tr>
                  Resource Type<\/td>Deployment<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                  If OpenShift auto-fills the names, you can keep the defaults as long as they are clear and unique.<\/p>\n\n\n\n
                  For consistency in this lab, use:<\/p>\n\n\n
                  Application Name: lab11-source-build\nName: sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                  \n\n\n\n
                  Part 8: Configure Resources<\/h1>\n\n\n\n
                  In the Resources<\/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
                  Why?<\/p>\n\n\n\n
                  Because Deployment<\/code> is the standard Kubernetes workload resource and is the preferred teaching choice for modern OpenShift labs.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 9: Create a Route<\/h1>\n\n\n\n
                  In the Advanced options<\/strong> section, make sure this option is enabled:<\/p>\n\n\n
                  Create a route to the application\n<\/code><\/span><\/pre>\n\n\n
                  A Route gives the application a browser-accessible URL.<\/p>\n\n\n\n
                  Without a Route, the application would still run inside the cluster, but you would not be able to open it easily from your browser.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 10: Create the Application<\/h1>\n\n\n\n
                  Review the form.<\/p>\n\n\n\n
                  You should have:<\/p>\n\n\n\n
                  Setting<\/th>Expected Value<\/th><\/tr><\/thead>
                  Project<\/td>lab11-source-build<\/code><\/td><\/tr>
                  Git Repo URL<\/td>https:\/\/github.com\/redhat-developer-demos\/sandbox-nodejs.git<\/code><\/td><\/tr>
                  Import Strategy<\/td>Builder Image<\/td><\/tr>
                  Builder Image<\/td>Node.js<\/td><\/tr>
                  Application Name<\/td>lab11-source-build<\/code><\/td><\/tr>
                  Name<\/td>sandbox-nodejs<\/code><\/td><\/tr>
                  Resource Type<\/td>Deployment<\/td><\/tr>
                  Create Route<\/td>Enabled<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                  Click:<\/p>\n\n\n
                  Create\n<\/code><\/span><\/pre>\n\n\n
                  OpenShift now starts the build and deployment process.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 11: Watch the Build in the Web Console<\/h1>\n\n\n\n
                  After you click Create<\/strong>, OpenShift takes you to the Topology<\/strong> view.<\/p>\n\n\n\n
                  You should see an application icon for:<\/p>\n\n\n
                  sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                  During the build, the ring around the application may show a build or progress state.<\/p>\n\n\n\n
                  Wait until the application is built and running.<\/p>\n\n\n\n
                  This may take a few minutes on OpenShift Local.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 12: View Build Logs in the Web Console<\/h1>\n\n\n\n
                  To view the build logs:<\/p>\n\n\n\n
                    \n
                  1. In Topology<\/strong>, click the sandbox-nodejs<\/code> application.<\/li>\n\n\n\n
                  2. Look for the related build.<\/li>\n\n\n\n
                  3. Open the build details.<\/li>\n\n\n\n
                  4. Click Logs<\/strong>.<\/li>\n<\/ol>\n\n\n\n
                    You should see OpenShift cloning the Git repository, installing dependencies, and assembling the application image.<\/p>\n\n\n\n
                    Typical log stages include:<\/p>\n\n\n
                    Cloning<\/span> source<\/span> code<\/span>\nInstalling<\/span> Node<\/span>.js<\/span> dependencies<\/span>\nRunning<\/span> S2I<\/span> assemble<\/span> process<\/span>\nPushing<\/span> image<\/span> to<\/span> internal<\/span> registry<\/span>\nBuild<\/span> completed<\/span> successfully<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                    Exact log text may differ depending on your builder image version.<\/p>\n\n\n\n
                    \n\n\n\n
                    Part 13: Verify the Application from the Web Console<\/h1>\n\n\n\n
                    In the Topology<\/strong> view:<\/p>\n\n\n\n
                      \n
                    1. Wait until the application shows as running.<\/li>\n\n\n\n
                    2. Click the external link icon on the application.<\/li>\n\n\n\n
                    3. A browser tab should open.<\/li>\n\n\n\n
                    4. The Node.js application page should load.<\/li>\n<\/ol>\n\n\n\n
                      If the page opens successfully, your source-code build and deployment worked.<\/p>\n\n\n\n
                      \n\n\n\n
                      Part 14: Verify Resources Using the CLI<\/h1>\n\n\n\n
                      Now validate the same result using the oc<\/code> CLI.<\/p>\n\n\n\n
                      Set the project:<\/p>\n\n\n
                      oc project lab11-source-build\n<\/code><\/span><\/pre>\n\n\n
                      List the main resources:<\/p>\n\n\n
                      oc get<\/span> buildconfig,build,imagestream,deployment,pod,service,route\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                      You should see resources similar to:<\/p>\n\n\n
                      buildconfig.build.openshift.io\/sandbox-nodejs\nbuild.build.openshift.io\/sandbox-nodejs-1\nimagestream.image.openshift.io\/sandbox-nodejs\ndeployment.apps\/sandbox-nodejs\npod\/sandbox-nodejs-xxxxx\nservice\/sandbox-nodejs\nroute.route.openshift.io\/sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                      The exact pod and build names may be different.<\/p>\n\n\n\n
                      \n\n\n\n
                      Part 15: Check the BuildConfig<\/h1>\n\n\n\n
                      Run:<\/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 output:<\/p>\n\n\n
                      NAME             TYPE     FROM          LATEST\nsandbox-nodejs   Source   Git           1\n<\/code><\/span><\/pre>\n\n\n
                      Describe the BuildConfig:<\/p>\n\n\n
                      oc describe bc sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                      Look for:<\/p>\n\n\n
                      Strategy<\/span>: Source<\/span>\nSource<\/span>: Git<\/span>\nOutput<\/span> to<\/span>: ImageStreamTag<\/span> sandbox-nodejs<\/span>:latest<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                      This confirms that OpenShift created a source build configuration.<\/p>\n\n\n\n
                      \n\n\n\n
                      Part 16: Check the Build<\/h1>\n\n\n\n
                      List 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
                      NAME               TYPE     FROM          STATUS     STARTED          DURATION\nsandbox-nodejs-1   Source   Git           Complete   ...              ...\n<\/code><\/span><\/pre>\n\n\n
                      The build status should be:<\/p>\n\n\n
                      Complete\n<\/code><\/span><\/pre>\n\n\n
                      View the build logs:<\/p>\n\n\n
                      oc logs -f bc\/sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                      If the build is already complete, this command still shows the latest BuildConfig logs.<\/p>\n\n\n\n
                      You can also view logs for a specific build:<\/p>\n\n\n
                      oc logs build\/sandbox-nodejs-1\n<\/code><\/span><\/pre>\n\n\n
                      \n\n\n\n
                      Part 17: Check the ImageStream<\/h1>\n\n\n\n
                      Run:<\/p>\n\n\n
                      oc get<\/span> imagestream\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                      Expected output:<\/p>\n\n\n
                      NAME             IMAGE REPOSITORY                                                   TAGS     UPDATED\nsandbox-nodejs   default<\/span>-route-openshift-image-registry.apps-crc.testing\/...        latest   ...\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                      The ImageStream tracks the image produced by the build.<\/p>\n\n\n\n
                      OpenShift uses this image to deploy the application.<\/p>\n\n\n\n
                      \n\n\n\n
                      Part 18: Check the Deployment<\/h1>\n\n\n\n
                      Run:<\/p>\n\n\n
                      oc get<\/span> deployment\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\nsandbox-nodejs   1\/1     1            1           ...\n<\/code><\/span><\/pre>\n\n\n
                      Check rollout status:<\/p>\n\n\n
                      oc rollout status deployment\/sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                      Expected output:<\/p>\n\n\n
                      deployment \"sandbox-nodejs\"<\/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 sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                      This shows the image, labels, pod template, replica count, and rollout status.<\/p>\n\n\n\n
                      \n\n\n\n
                      Part 19: 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\nsandbox-nodejs-xxxxx              1\/1     Running     0          ...\n<\/code><\/span><\/pre>\n\n\n
                      View pod logs:<\/p>\n\n\n
                      oc logs deployment\/sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                      Expected output may include Node.js or Express startup logs.<\/p>\n\n\n\n
                      If the pod is not running, describe it:<\/p>\n\n\n
                      oc describe pod -l app=sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                      \n\n\n\n
                      Part 20: Check the Service<\/h1>\n\n\n\n
                      Run:<\/p>\n\n\n
                      oc get<\/span> svc\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\nsandbox-nodejs   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 stable internal access to the application inside the cluster.<\/p>\n\n\n\n
                      The Service name is:<\/p>\n\n\n
                      sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                      Inside the same project, other pods can reach the app using:<\/p>\n\n\n
                      http:\/\/sandbox-nodejs:8080<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                      \n\n\n\n
                      Part 21: Check the Route<\/h1>\n\n\n\n
                      Run:<\/p>\n\n\n
                      oc get<\/span> route\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                                             PATH   SERVICES         PORT     TERMINATION   WILDCARD\nsandbox-nodejs   sandbox-nodejs-lab11-source-build.apps-crc.testing            sandbox-nodejs   8080                   None\n<\/code><\/span><\/pre>\n\n\n
                      The exact hostname may be different.<\/p>\n\n\n\n
                      Store the route URL:<\/p>\n\n\n
                      APP_URL=\"http:\/\/$(oc get route sandbox-nodejs -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 application:<\/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 output should include:<\/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
                      If your application redirects or returns another successful HTTP response, that is also acceptable.<\/p>\n\n\n\n
                      Open the URL in your browser:<\/p>\n\n\n
                      http:\/\/<route-hostname<\/span>><\/span>\n<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
                      \n\n\n\n
                      Part 22: Understand What Happened<\/h1>\n\n\n\n
                      When you clicked Create<\/strong>, OpenShift performed several actions automatically.<\/p>\n\n\n\n
                      Step 1: OpenShift Pulled Source Code from Git<\/h2>\n\n\n\n
                      OpenShift cloned the repository:<\/p>\n\n\n
                      https:\/\/github.com\/redhat-developer-demos\/sandbox-nodejs.git<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                      Step 2: OpenShift Selected a Builder Image<\/h2>\n\n\n\n
                      Because this is a Node.js application, OpenShift used a Node.js builder image.<\/p>\n\n\n\n
                      Step 3: OpenShift Created a BuildConfig<\/h2>\n\n\n\n
                      The BuildConfig stores the build definition.<\/p>\n\n\n\n
                      It tells OpenShift:<\/p>\n\n\n
                      Where the source code is\nWhich builder image to use<\/span>\nWhere<\/span> to<\/span> push<\/span> the<\/span> built<\/span> image<\/span>\nWhat<\/span> triggers<\/span> future<\/span> builds<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                      Step 4: OpenShift Started a Build<\/h2>\n\n\n\n
                      The Build object represents one execution of the build.<\/p>\n\n\n\n
                      Example:<\/p>\n\n\n
                      sandbox-nodejs-1\n<\/code><\/span><\/pre>\n\n\n
                      Step 5: OpenShift Created an ImageStream<\/h2>\n\n\n\n
                      The ImageStream tracks the resulting image.<\/p>\n\n\n\n
                      The app Deployment points to the image produced by the build.<\/p>\n\n\n\n
                      Step 6: OpenShift Created a Deployment<\/h2>\n\n\n\n
                      The Deployment created the running application pod.<\/p>\n\n\n\n
                      Step 7: OpenShift Created a Service<\/h2>\n\n\n\n
                      The Service provides internal access to the pod.<\/p>\n\n\n\n
                      Step 8: OpenShift Created a Route<\/h2>\n\n\n\n
                      The Route provides external browser access to the application.<\/p>\n\n\n\n
                      \n\n\n\n
                      Part 23: Trigger a New Build Manually<\/h1>\n\n\n\n
                      You can manually trigger a rebuild.<\/p>\n\n\n\n
                      Run:<\/p>\n\n\n
                      oc start-build sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                      Expected output:<\/p>\n\n\n
                      build.build.openshift.io\/sandbox-nodejs-2 started\n<\/code><\/span><\/pre>\n\n\n
                      Watch the build:<\/p>\n\n\n
                      oc logs -f bc\/sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                      List builds again:<\/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
                      NAME               TYPE     FROM          STATUS\nsandbox-nodejs-1   Source   Git           Complete\nsandbox-nodejs-2   Source   Git           Complete\n<\/code><\/span><\/pre>\n\n\n
                      This proves that the BuildConfig can be reused to produce a new application image.<\/p>\n\n\n\n
                      \n\n\n\n
                      Part 24: Scale the Application<\/h1>\n\n\n\n
                      Even though this lab focuses on building from source code, you can quickly verify that the result is a normal Kubernetes Deployment.<\/p>\n\n\n\n
                      Scale to 2 pods:<\/p>\n\n\n
                      oc scale deployment\/sandbox-nodejs --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 sandbox-nodejs pods should be running.\n<\/code><\/span><\/pre>\n\n\n
                      Scale back to 1 pod:<\/p>\n\n\n
                      oc scale deployment\/sandbox-nodejs --replicas=1\n<\/code><\/span><\/pre>\n\n\n
                      Check deployment:<\/p>\n\n\n
                      oc get<\/span> deployment sandbox-nodejs\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                      Expected result:<\/p>\n\n\n
                      READY   1\/1\n<\/code><\/span><\/pre>\n\n\n
                      \n\n\n\n
                      Part 25: Optional CLI-Only Equivalent<\/h1>\n\n\n\n
                      The main lab uses the web console. However, it is useful to know the CLI equivalent.<\/p>\n\n\n\n
                      To create a similar app from source code using the CLI, you could run:<\/p>\n\n\n
                      oc new<\/span>-app https:\/\/github.com\/redhat-developer-demos\/sandbox-nodejs.git --name=sandbox-nodejs<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                      Then expose it:<\/p>\n\n\n
                      oc expose svc\/sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                      Check the route:<\/p>\n\n\n
                      oc get<\/span> route sandbox-nodejs\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                      This is not the main method for this lab, but it helps students understand that the web console and CLI both create OpenShift resources.<\/p>\n\n\n\n
                      \n\n\n\n
                      Part 26: Student Validation Checklist<\/h1>\n\n\n\n
                      Students should confirm the following:<\/p>\n\n\n\n
                      Check<\/th>Command<\/th>Expected Result<\/th><\/tr><\/thead>
                      Current project<\/td>oc project<\/code><\/td>lab11-source-build<\/code><\/td><\/tr>
                      BuildConfig exists<\/td>oc get bc<\/code><\/td>sandbox-nodejs<\/code><\/td><\/tr>
                      Build completed<\/td>oc get builds<\/code><\/td>Build status Complete<\/code><\/td><\/tr>
                      ImageStream exists<\/td>oc get is<\/code><\/td>sandbox-nodejs<\/code><\/td><\/tr>
                      Deployment ready<\/td>oc get deploy<\/code><\/td>1\/1<\/code> ready<\/td><\/tr>
                      Pod running<\/td>oc get pods<\/code><\/td>Pod status Running<\/code><\/td><\/tr>
                      Service exists<\/td>oc get svc<\/code><\/td>sandbox-nodejs<\/code><\/td><\/tr>
                      Route exists<\/td>oc get route<\/code><\/td>Route hostname created<\/td><\/tr>
                      Browser works<\/td>Open route URL<\/td>App page loads<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                      \n\n\n\n
                      Part 27: Full Validation Commands<\/h1>\n\n\n\n
                      Run these commands after completing the lab:<\/p>\n\n\n
                      oc project lab11-source-build\n\necho<\/span> \"Checking BuildConfig...\"<\/span>\noc get bc sandbox-nodejs\n\necho<\/span> \"Checking Builds...\"<\/span>\noc get builds\n\necho<\/span> \"Checking ImageStream...\"<\/span>\noc get imagestream sandbox-nodejs\n\necho<\/span> \"Checking Deployment...\"<\/span>\noc get deployment sandbox-nodejs\n\necho<\/span> \"Checking rollout status...\"<\/span>\noc rollout status deployment\/sandbox-nodejs\n\necho<\/span> \"Checking Pods...\"<\/span>\noc get pods -l app=sandbox-nodejs\n\necho<\/span> \"Checking Service...\"<\/span>\noc get svc sandbox-nodejs\n\necho<\/span> \"Checking Route...\"<\/span>\noc get route sandbox-nodejs\n\necho<\/span> \"Getting app URL...\"<\/span>\nAPP_URL=\"http:\/\/$(oc get route sandbox-nodejs -o jsonpath='{.spec.host}')\"<\/span>\necho<\/span> \"$APP_URL\"<\/span>\n\necho<\/span> \"Testing app...\"<\/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. BuildConfig exists.<\/li>\n\n\n\n
                      2. Build status is Complete<\/code>.<\/li>\n\n\n\n
                      3. ImageStream exists.<\/li>\n\n\n\n
                      4. Deployment is available.<\/li>\n\n\n\n
                      5. Pod is running.<\/li>\n\n\n\n
                      6. Service exists.<\/li>\n\n\n\n
                      7. Route exists.<\/li>\n\n\n\n
                      8. curl -I<\/code> returns an HTTP response.<\/li>\n<\/ol>\n\n\n\n
                        \n\n\n\n
                        Part 28: Troubleshooting<\/h1>\n\n\n\n
                        Problem 1: Git Repository URL Is Not Validated<\/h2>\n\n\n\n
                        Symptom<\/h3>\n\n\n\n
                        The web console does not validate the Git URL.<\/p>\n\n\n\n
                        Possible Causes<\/h3>\n\n\n\n
                          \n
                        1. Internet connection issue.<\/li>\n\n\n\n
                        2. GitHub is blocked by network policy or firewall.<\/li>\n\n\n\n
                        3. Typo in the repository URL.<\/li>\n\n\n\n
                        4. OpenShift Local VM cannot reach GitHub.<\/li>\n<\/ol>\n\n\n\n
                          Fix<\/h3>\n\n\n\n
                          Check the URL:<\/p>\n\n\n
                          https:\/\/github.com\/redhat-developer-demos\/sandbox-nodejs.git<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                          Try opening the repository in your browser.<\/p>\n\n\n\n
                          From CLI, check whether your OpenShift Local cluster is running:<\/p>\n\n\n
                          crc status\n<\/code><\/span><\/pre>\n\n\n
                          \n\n\n\n
                          Problem 2: Builder Image Is Not Detected<\/h2>\n\n\n\n
                          Symptom<\/h3>\n\n\n\n
                          OpenShift does not automatically detect Node.js.<\/p>\n\n\n\n
                          Possible Causes<\/h3>\n\n\n\n
                            \n
                          1. Builder images are not available in your local OpenShift environment.<\/li>\n\n\n\n
                          2. The Cluster Samples Operator did not install sample image streams.<\/li>\n\n\n\n
                          3. The Git repository was not detected properly.<\/li>\n<\/ol>\n\n\n\n
                            Fix<\/h3>\n\n\n\n
                            In the Import from Git page, manually select:<\/p>\n\n\n
                            Import<\/span> Strategy<\/span>: Builder<\/span> Image<\/span>\nBuilder<\/span> Image<\/span>: Node<\/span>.js<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                            If Node.js is not available, ask the instructor to check cluster sample image streams.<\/p>\n\n\n\n
                            The instructor can check:<\/p>\n\n\n
                            oc get<\/span> imagestream -n openshift | grep -i node\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            If no Node.js image stream exists, the OpenShift Local sample image configuration may need review.<\/p>\n\n\n\n
                            \n\n\n\n
                            Problem 3: Build Fails During npm Install<\/h2>\n\n\n\n
                            Symptom<\/h3>\n\n\n\n
                            The build starts but fails while installing Node.js dependencies.<\/p>\n\n\n\n
                            Possible Causes<\/h3>\n\n\n\n
                              \n
                            1. Network issue while downloading npm packages.<\/li>\n\n\n\n
                            2. Temporary npm registry issue.<\/li>\n\n\n\n
                            3. Resource constraints in OpenShift Local.<\/li>\n\n\n\n
                            4. Builder image issue.<\/li>\n<\/ol>\n\n\n\n
                              Fix<\/h3>\n\n\n\n
                              Check build logs:<\/p>\n\n\n
                              oc logs -f bc\/sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                              Check build status:<\/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
                              Describe the failed build:<\/p>\n\n\n
                              oc describe build sandbox-nodejs-1\n<\/code><\/span><\/pre>\n\n\n
                              Try the build again:<\/p>\n\n\n
                              oc start-build sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                              \n\n\n\n
                              Problem 4: Pod Is Not Running<\/h2>\n\n\n\n
                              Symptom<\/h3>\n\n\n\n
                              The build succeeds, but the pod does not become ready.<\/p>\n\n\n\n
                              Fix<\/h3>\n\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
                              Describe the pod:<\/p>\n\n\n
                              oc describe pod -l app=sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                              Check logs:<\/p>\n\n\n
                              oc logs deployment\/sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                              Common causes:<\/p>\n\n\n\n
                                \n
                              1. Application startup error.<\/li>\n\n\n\n
                              2. Wrong runtime port.<\/li>\n\n\n\n
                              3. Insufficient memory.<\/li>\n\n\n\n
                              4. Image pull issue.<\/li>\n\n\n\n
                              5. CrashLoopBackOff.<\/li>\n<\/ol>\n\n\n\n
                                \n\n\n\n
                                Problem 5: Route Opens but Browser Shows Error<\/h2>\n\n\n\n
                                Symptom<\/h3>\n\n\n\n
                                The route exists, but the application page does not load.<\/p>\n\n\n\n
                                Fix<\/h3>\n\n\n\n
                                Check the route:<\/p>\n\n\n
                                oc get<\/span> route sandbox-nodejs\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                Check the service:<\/p>\n\n\n
                                oc get<\/span> svc sandbox-nodejs\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 sandbox-nodejs\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 a running 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 sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                                \n\n\n\n
                                Problem 6: curl<\/code> Does Not Work Locally<\/h2>\n\n\n\n
                                Symptom<\/h3>\n\n\n\n
                                The browser works but local curl<\/code> fails, or curl<\/code> works but browser fails.<\/p>\n\n\n\n
                                Possible Causes<\/h3>\n\n\n\n
                                  \n
                                1. DNS issue on local machine.<\/li>\n\n\n\n
                                2. Browser proxy or VPN issue.<\/li>\n\n\n\n
                                3. CRC networking issue.<\/li>\n\n\n\n
                                4. Application not ready yet.<\/li>\n<\/ol>\n\n\n\n
                                  Fix<\/h3>\n\n\n\n
                                  Check CRC status:<\/p>\n\n\n
                                  crc status\n<\/code><\/span><\/pre>\n\n\n
                                  Print route:<\/p>\n\n\n
                                  oc get<\/span> route sandbox-nodejs\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
                                  Problem 7: BuildConfig Not Found<\/h2>\n\n\n\n
                                  Symptom<\/h3>\n\n\n\n
                                  This command fails:<\/p>\n\n\n
                                  oc get<\/span> bc sandbox-nodejs\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                  Possible Causes<\/h3>\n\n\n\n
                                    \n
                                  1. You are in the wrong project.<\/li>\n\n\n\n
                                  2. The application name is different.<\/li>\n\n\n\n
                                  3. The import failed.<\/li>\n\n\n\n
                                  4. The web console created resources with a different name.<\/li>\n<\/ol>\n\n\n\n
                                    Fix<\/h3>\n\n\n\n
                                    Check current project:<\/p>\n\n\n
                                    oc project\n<\/code><\/span><\/pre>\n\n\n
                                    Switch to the correct project:<\/p>\n\n\n
                                    oc project lab11-source-build\n<\/code><\/span><\/pre>\n\n\n
                                    List all BuildConfigs:<\/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
                                    List all 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
                                    \n\n\n\n
                                    Part 29: Cleanup<\/h1>\n\n\n\n
                                    You can delete the application only, or delete the whole project.<\/p>\n\n\n\n
                                    For a lab environment, deleting the whole project is easiest.<\/p>\n\n\n\n
                                    Cleanup from Web Console<\/h2>\n\n\n\n
                                      \n
                                    1. Switch to the Developer<\/strong> perspective.<\/li>\n\n\n\n
                                    2. Open the project:<\/li>\n<\/ol>\n\n\n
                                      lab11-source-build\n<\/code><\/span><\/pre>\n\n\n
                                        \n
                                      1. Go to Topology<\/strong>.<\/li>\n\n\n\n
                                      2. Right-click the sandbox-nodejs<\/code> application.<\/li>\n\n\n\n
                                      3. Select Delete Application<\/strong>.<\/li>\n\n\n\n
                                      4. Confirm the deletion.<\/li>\n<\/ol>\n\n\n\n
                                        This removes the application resources but may not remove every project-level object.<\/p>\n\n\n\n
                                        \n\n\n\n
                                        Cleanup from CLI<\/h2>\n\n\n\n
                                        Delete the whole project:<\/p>\n\n\n
                                        oc delete<\/span> project lab11-source-build\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 lab11-source-build\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                        Expected result:<\/p>\n\n\n
                                        Error<\/span> from<\/span> server (NotFound): projects.project.openshift.io \"lab11-source-build\"<\/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 30: Lab Summary<\/h1>\n\n\n\n
                                        In this lab, you built and deployed an application from source code using the OpenShift web console.<\/p>\n\n\n\n
                                        You learned that OpenShift can:<\/p>\n\n\n\n
                                          \n
                                        1. Pull source code from Git.<\/li>\n\n\n\n
                                        2. Detect or use a builder image.<\/li>\n\n\n\n
                                        3. Build a runnable container image using S2I.<\/li>\n\n\n\n
                                        4. Store the built image in an ImageStream.<\/li>\n\n\n\n
                                        5. Deploy the image as a Kubernetes Deployment.<\/li>\n\n\n\n
                                        6. Run the application in a Pod.<\/li>\n\n\n\n
                                        7. Expose the application internally using a Service.<\/li>\n\n\n\n
                                        8. Expose the application externally using a Route.<\/li>\n\n\n\n
                                        9. Allow rebuilds using a BuildConfig.<\/li>\n<\/ol>\n\n\n\n
                                          \n\n\n\n
                                          Part 31: Review Questions<\/h1>\n\n\n\n
                                          Question 1<\/h2>\n\n\n\n
                                          What is the purpose of Source-to-Image?<\/p>\n\n\n\n
                                          Answer<\/h3>\n\n\n\n
                                          Source-to-Image builds a runnable container image by combining application source code with a builder image.<\/p>\n\n\n\n
                                          \n\n\n\n
                                          Question 2<\/h2>\n\n\n\n
                                          What does a BuildConfig do?<\/p>\n\n\n\n
                                          Answer<\/h3>\n\n\n\n
                                          A BuildConfig defines how OpenShift should build an application, including the source repository, build strategy, builder image, triggers, and output image.<\/p>\n\n\n\n
                                          \n\n\n\n
                                          Question 3<\/h2>\n\n\n\n
                                          What is the purpose of an ImageStream?<\/p>\n\n\n\n
                                          Answer<\/h3>\n\n\n\n
                                          An ImageStream tracks container images inside OpenShift and allows OpenShift resources to refer to images using tags such as latest<\/code>.<\/p>\n\n\n\n
                                          \n\n\n\n
                                          Question 4<\/h2>\n\n\n\n
                                          Why did we choose Deployment instead of DeploymentConfig?<\/p>\n\n\n\n
                                          Answer<\/h3>\n\n\n\n
                                          Deployment is the standard Kubernetes workload resource and is the better choice for modern beginner labs.<\/p>\n\n\n\n
                                          \n\n\n\n
                                          Question 5<\/h2>\n\n\n\n
                                          What is the purpose of a Service?<\/p>\n\n\n\n
                                          Answer<\/h3>\n\n\n\n
                                          A Service provides stable internal network access to application pods.<\/p>\n\n\n\n
                                          \n\n\n\n
                                          Question 6<\/h2>\n\n\n\n
                                          What is the purpose of a Route?<\/p>\n\n\n\n
                                          Answer<\/h3>\n\n\n\n
                                          A Route exposes an application outside the OpenShift cluster using a browser-accessible hostname.<\/p>\n\n\n\n
                                          \n\n\n\n
                                          Question 7<\/h2>\n\n\n\n
                                          Which command shows the latest build logs from a BuildConfig?<\/p>\n\n\n\n
                                          Answer<\/h3>\n\n\n
                                          oc logs -f bc\/sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                                          \n\n\n\n
                                          Question 8<\/h2>\n\n\n\n
                                          Which command manually triggers a new build?<\/p>\n\n\n\n
                                          Answer<\/h3>\n\n\n
                                          oc start-build sandbox-nodejs\n<\/code><\/span><\/pre>\n\n\n
                                          \n\n\n\n
                                          Question 9<\/h2>\n\n\n\n
                                          Which command shows the external application URL?<\/p>\n\n\n\n
                                          Answer<\/h3>\n\n\n
                                          oc get<\/span> route sandbox-nodejs\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
                                          Which command deletes the whole lab project?<\/p>\n\n\n\n
                                          Answer<\/h3>\n\n\n
                                          oc delete<\/span> project lab11-source-build\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                          \n\n\n\n
                                          Part 32: Instructor Notes<\/h1>\n\n\n\n
                                          This lab is designed as a modern replacement for older OpenShift source-code build labs.<\/p>\n\n\n\n
                                          The old lab flow was based on Developer Sandbox. This replacement uses OpenShift Local so that students can practice locally.<\/p>\n\n\n\n
                                          This lab intentionally uses:<\/p>\n\n\n
                                          Deployment\n<\/code><\/span><\/pre>\n\n\n
                                          instead of:<\/p>\n\n\n
                                          DeploymentConfig\n<\/code><\/span><\/pre>\n\n\n
                                          This is better for students because it aligns with standard Kubernetes workload concepts.<\/p>\n\n\n\n
                                          The lab also uses a simple Node.js Git repository so students can focus on the OpenShift build process rather than database setup, application debugging, or complex runtime dependencies.<\/p>\n\n\n\n
                                          For a more advanced course, follow-up labs can cover:<\/p>\n\n\n\n
                                            \n
                                          1. Building from a Dockerfile.<\/li>\n\n\n\n
                                          2. Building from a private Git repository.<\/li>\n\n\n\n
                                          3. Using source clone secrets.<\/li>\n\n\n\n
                                          4. Using Git webhooks.<\/li>\n\n\n\n
                                          5. Setting build triggers.<\/li>\n\n\n\n
                                          6. Setting build CPU and memory limits.<\/li>\n\n\n\n
                                          7. Rolling back deployments.<\/li>\n\n\n\n
                                          8. Using OpenShift Pipelines.<\/li>\n\n\n\n
                                          9. Using GitOps.<\/li>\n\n\n\n
                                          10. Deploying multi-service applications.<\/li>\n<\/ol>\n\n\n\n
                                            \n\n\n\n
                                            Part 33: Instructor Pre-Validation Checklist<\/h1>\n\n\n\n
                                            Before giving this lab to students, the instructor should run:<\/p>\n\n\n
                                            crc version\ncrc status\noc version\noc whoami\noc get<\/span> nodes\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                            Check that the developer user can create projects:<\/p>\n\n\n
                                            oc auth can-i create projects\n<\/code><\/span><\/pre>\n\n\n
                                            Check that Node.js builder image streams are available:<\/p>\n\n\n
                                            oc get<\/span> imagestream -n openshift | grep -i node\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                            Create a test project:<\/p>\n\n\n
                                            oc new<\/span>-project lab11-source-build-test\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                            Optionally test the CLI equivalent:<\/p>\n\n\n
                                            oc new<\/span>-app https:\/\/github.com\/redhat-developer-demos\/sandbox-nodejs.git --name=sandbox-nodejs<\/span>\noc expose svc\/sandbox-nodejs\noc rollout status deployment\/sandbox-nodejs\noc get<\/span> route sandbox-nodejs\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 sandbox-nodejs -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:<\/p>\n\n\n
                                            oc delete<\/span> project lab11-source-build-test\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                            If these checks 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 built and deployed an application from source code using the OpenShift web console.<\/p>\n\n\n\n
                                            You now understand the complete OpenShift source-build workflow:<\/p>\n\n\n
                                            Git Repository\n  -> Source-to-Image Build\n  -> BuildConfig\n  -> Build\n  -> ImageStream\n  -> Deployment\n  -> Pod\n  -> Service\n  -> Route\n  -> Browser\n<\/code><\/span><\/pre>\n\n\n
                                            This is one of the most important OpenShift developer workflows because it allows developers to go from source code to a running application without manually writing a container image build command.<\/p>\n","protected":false},"excerpt":{"rendered":"
                                            Lab Objective In this lab, you will build and deploy a web application from source code stored in a Git repository using the OpenShift web console. You… <\/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-50032","post","type-post","status-publish","format-standard","hentry","category-openshift"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/50032","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=50032"}],"version-history":[{"count":4,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/50032\/revisions"}],"predecessor-version":[{"id":77161,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/50032\/revisions\/77161"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=50032"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=50032"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=50032"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}