{"id":50040,"date":"2026-06-23T08:23:56","date_gmt":"2026-06-23T08:23:56","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=50040"},"modified":"2026-06-23T08:23:59","modified_gmt":"2026-06-23T08:23:59","slug":"openshift-setting-up-and-using-openshift-serverless-functions","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/openshift-setting-up-and-using-openshift-serverless-functions\/","title":{"rendered":"OpenShift Lab 14: Setting Up and Using OpenShift Serverless Functions on OpenShift Local"},"content":{"rendered":"\n

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

In this lab, you will install and use OpenShift Serverless Functions on OpenShift Local.<\/p>\n\n\n\n

You will create a simple Node.js serverless function, deploy it to OpenShift, invoke it using HTTP, verify the Knative resources created by OpenShift Serverless, and observe scale-to-zero behavior.<\/p>\n\n\n\n

This lab is a modern replacement for the older \u201cSetting up and using OpenShift Serverless Functions\u201d article. The original article explains the concept, but this replacement provides a complete hands-on lab for students.<\/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 as both developer<\/code> and kubeadmin<\/code>.<\/li>\n\n\n\n
  3. Install the OpenShift Serverless Operator.<\/li>\n\n\n\n
  4. Install Knative Serving.<\/li>\n\n\n\n
  5. Install and validate the Knative kn<\/code> CLI.<\/li>\n\n\n\n
  6. Prepare an image registry for function images.<\/li>\n\n\n\n
  7. Create a new project for functions.<\/li>\n\n\n\n
  8. Create a Node.js function using kn func<\/code>.<\/li>\n\n\n\n
  9. Modify the function code.<\/li>\n\n\n\n
  10. Deploy the function as a Knative Service.<\/li>\n\n\n\n
  11. Invoke the function.<\/li>\n\n\n\n
  12. Validate Knative Service, Revision, Configuration, and Route resources.<\/li>\n\n\n\n
  13. Observe scale-to-zero and scale-from-zero.<\/li>\n\n\n\n
  14. View function logs.<\/li>\n\n\n\n
  15. Troubleshoot common OpenShift Serverless issues.<\/li>\n\n\n\n
  16. Clean up the lab environment.<\/li>\n<\/ol>\n\n\n\n
    \n\n\n\n

    Lab Architecture<\/h2>\n\n\n
    Developer Machine\n  |\n  | kn func create\n  | kn func deploy\n  | kn func invoke\n  v\nOpenShift Local\n  |\n  v\nOpenShift Serverless Operator\n  |\n  v\nKnative Serving\n  |\n  v\nKnative Service\n  |\n  v\nRevision\n  |\n  v\nPod\n  |\n  v\nKnative Route\n  |\n  v\nFunction<\/span> URL\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
    \n\n\n\n
    What Is OpenShift Serverless?<\/h2>\n\n\n\n
    OpenShift Serverless allows you to run applications and functions that automatically scale based on demand.<\/p>\n\n\n\n
    It is based on Knative.<\/p>\n\n\n\n
    In simple terms:<\/p>\n\n\n
    Normal Deployment:\nApplication pod usually keeps running.\n\nServerless Function<\/span>:\nFunction<\/span> pod starts when traffic arrives.\nFunction pod can scale down to zero when idle.\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
    \n\n\n\n
    What Is a Serverless Function?<\/h2>\n\n\n\n
    A serverless function is a small piece of code that runs in response to a request or event.<\/p>\n\n\n\n
    Examples:<\/p>\n\n\n
    HTTP request\nCloudEvent\nMessage from<\/span> a queue\nKafka event\nWebhook event\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
    In this beginner lab, you will use a simple HTTP function.<\/p>\n\n\n\n
    \n\n\n\n
    Important Concept: Function vs Deployment<\/h2>\n\n\n\n
    Area<\/th>Normal OpenShift Deployment<\/th>OpenShift Serverless Function<\/th><\/tr><\/thead>
    Main resource<\/td>Deployment<\/td>Knative Service<\/td><\/tr>
    Scaling<\/td>Manual, HPA, or custom autoscaling<\/td>Automatic request-based scaling<\/td><\/tr>
    Scale to zero<\/td>Not by default<\/td>Yes<\/td><\/tr>
    Route handling<\/td>OpenShift Route<\/td>Knative Route<\/td><\/tr>
    Build\/deploy tool<\/td>oc<\/code>, Git, pipelines, image deploy<\/td>kn func<\/code><\/td><\/tr>
    Good for<\/td>Long-running apps<\/td>Event-driven or request-driven workloads<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    \n\n\n\n
    Important Concept: Function vs Knative Service<\/h2>\n\n\n\n
    A function is a developer workflow.<\/p>\n\n\n\n
    A Knative Service is the runtime resource created after the function is deployed.<\/p>\n\n\n
    Function<\/span> source code\n  -> container image\n  -> Knative Service\n  -> Revision\n  -> Pod\n  -> URL\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
    When you run:<\/p>\n\n\n
    kn func deploy\n<\/code><\/span><\/pre>\n\n\n
    OpenShift packages your function into a container image and deploys it as a Knative Service.<\/p>\n\n\n\n
    \n\n\n\n
    Important Lab Note: Admin and Student Responsibilities<\/h2>\n\n\n\n
    This lab has two parts.<\/p>\n\n\n\n
    Part<\/th>Who Runs It<\/th>Purpose<\/th><\/tr><\/thead>
    Admin setup<\/td>Instructor or cluster admin<\/td>Install OpenShift Serverless Operator and Knative Serving<\/td><\/tr>
    Student lab<\/td>Developer user<\/td>Create, deploy, invoke, and observe a function<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    A normal developer<\/code> user cannot install cluster operators. The operator setup must be done by kubeadmin<\/code> or another cluster administrator.<\/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. crc<\/code> command available.<\/li>\n\n\n\n
    3. oc<\/code> command available.<\/li>\n\n\n\n
    4. kn<\/code> CLI installed.<\/li>\n\n\n\n
    5. Podman or Docker installed.<\/li>\n\n\n\n
    6. Browser access to OpenShift web console.<\/li>\n\n\n\n
    7. Internet access from OpenShift Local.<\/li>\n\n\n\n
    8. Red Hat pull secret configured for OpenShift Local.<\/li>\n\n\n\n
    9. Enough CPU and memory for Serverless components.<\/li>\n<\/ol>\n\n\n\n
      \n\n\n\n
      Recommended OpenShift Local Resources<\/h2>\n\n\n\n
      OpenShift Serverless needs more resources than a simple Deployment lab.<\/p>\n\n\n\n
      Recommended OpenShift Local configuration:<\/p>\n\n\n\n
      Resource<\/th>Recommended<\/th><\/tr><\/thead>
      CPU<\/td>6 cores<\/td><\/tr>
      Memory<\/td>16 GB<\/td><\/tr>
      Disk<\/td>50 GB<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
      Configure CRC before starting the cluster:<\/p>\n\n\n
      crc config set<\/span> preset openshift\ncrc config set<\/span> cpus 6\ncrc config set<\/span> memory 16384\ncrc config set<\/span> disk-size 50\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
      If CRC is already running, stop it first:<\/p>\n\n\n
      crc stop\n<\/code><\/span><\/pre>\n\n\n
      Then start again after changing resources.<\/p>\n\n\n\n
      \n\n\n\n
      Part 2: Start OpenShift Local<\/h1>\n\n\n\n
      Run:<\/p>\n\n\n
      crc version\n<\/code><\/span><\/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
      View 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
      Open the 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:<\/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>.<\/p>\n\n\n\n
      Log in as developer<\/code> first:<\/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
      Verify:<\/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
      Now log in as kubeadmin<\/code> for the admin setup section:<\/p>\n\n\n
      oc login -u kubeadmin 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 kubeadmin<\/code> 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:<\/p>\n\n\n
      oc whoami\n<\/code><\/span><\/pre>\n\n\n
      Expected output:<\/p>\n\n\n
      kubeadmin\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 result:<\/p>\n\n\n
      crc-xxxxx-master-0   Ready\n<\/code><\/span><\/pre>\n\n\n
      \n\n\n\n
      Part 4: Install the OpenShift Serverless Operator<\/h1>\n\n\n\n
      This section must be done by kubeadmin<\/code> or a cluster administrator.<\/p>\n\n\n\n
      You can install the Operator from the web console or CLI.<\/p>\n\n\n\n
      \n\n\n\n
      Option A: Install from the Web Console<\/h2>\n\n\n\n
        \n
      1. Log in to the OpenShift web console as kubeadmin<\/code>.<\/li>\n\n\n\n
      2. Switch to Administrator<\/strong> perspective.<\/li>\n\n\n\n
      3. Go to Operators > OperatorHub<\/strong>.<\/li>\n\n\n\n
      4. Search for:<\/li>\n<\/ol>\n\n\n
        OpenShift Serverless Operator\n<\/code><\/span><\/pre>\n\n\n
          \n
        1. Click the Operator.<\/li>\n\n\n\n
        2. Click Install<\/strong>.<\/li>\n\n\n\n
        3. Use these settings:<\/li>\n<\/ol>\n\n\n\n
          Setting<\/th>Value<\/th><\/tr><\/thead>
          Installation mode<\/td>All namespaces on the cluster<\/td><\/tr>
          Installed namespace<\/td>openshift-serverless<\/code><\/td><\/tr>
          Update channel<\/td>stable<\/code><\/td><\/tr>
          Approval strategy<\/td>Automatic<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
            \n
          1. Click Install<\/strong>.<\/li>\n\n\n\n
          2. Wait until the Operator status shows:<\/li>\n<\/ol>\n\n\n
            Succeeded\n<\/code><\/span><\/pre>\n\n\n
            \n\n\n\n
            Option B: Install from CLI<\/h2>\n\n\n\n
            Create the Operator subscription YAML:<\/p>\n\n\n
            cat <<'EOF'<\/span> > serverless-operator.yaml\napiVersion<\/span>: v1\nkind<\/span>: Namespace\nmetadata<\/span>:\n  name: openshift-serverless\n---\napiVersion: operators.coreos.com\/v1\nkind<\/span>: OperatorGroup\nmetadata<\/span>:\n  name: serverless-operators\n  namespace<\/span>: openshift-serverless\nspec<\/span>: {}\n---\napiVersion: operators.coreos.com\/v1alpha1\nkind<\/span>: Subscription\nmetadata<\/span>:\n  name: serverless-operator\n  namespace<\/span>: openshift-serverless\nspec<\/span>:\n  channel: stable\n  installPlanApproval<\/span>: Automatic\n  name<\/span>: serverless-operator\n  source<\/span>: redhat-operators\n  sourceNamespace<\/span>: openshift-marketplace\nEOF\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
            Apply it:<\/p>\n\n\n
            oc<\/span> apply<\/span> -f<\/span> serverless-operator<\/span>.yaml<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
            Watch the installation:<\/p>\n\n\n
            oc get<\/span> pods -n openshift-serverless\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
            Check ClusterServiceVersion status:<\/p>\n\n\n
            oc get<\/span> csv -n openshift-serverless\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
            Wait until the CSV phase is:<\/p>\n\n\n
            Succeeded\n<\/code><\/span><\/pre>\n\n\n
            You can watch it with:<\/p>\n\n\n
            watch oc get<\/span> csv -n openshift-serverless\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
            If watch<\/code> is not available, run this repeatedly:<\/p>\n\n\n
            oc get<\/span> csv -n openshift-serverless\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
            \n\n\n\n
            Part 5: Install Knative Serving<\/h1>\n\n\n\n
            OpenShift Serverless Operator alone is not enough. To run functions, you must install Knative Serving.<\/p>\n\n\n\n
            Knative Serving allows you to create Knative Services and serverless functions.<\/p>\n\n\n\n
            \n\n\n\n
            Option A: Install Knative Serving from Web Console<\/h2>\n\n\n\n
              \n
            1. Log in as kubeadmin<\/code>.<\/li>\n\n\n\n
            2. Switch to Administrator<\/strong> perspective.<\/li>\n\n\n\n
            3. Go to Operators > Installed Operators<\/strong>.<\/li>\n\n\n\n
            4. Select project:<\/li>\n<\/ol>\n\n\n
              knative-serving\n<\/code><\/span><\/pre>\n\n\n
              If the project does not exist yet, create it from Home > Projects > Create Project<\/strong>.<\/p>\n\n\n\n
                \n
              1. Click OpenShift Serverless Operator<\/strong>.<\/li>\n\n\n\n
              2. Find Knative Serving<\/strong> under provided APIs.<\/li>\n\n\n\n
              3. Click Create Knative Serving<\/strong>.<\/li>\n\n\n\n
              4. Keep the default settings.<\/li>\n\n\n\n
              5. Click Create<\/strong>.<\/li>\n<\/ol>\n\n\n\n
                Wait until the KnativeServing<\/code> resource is ready.<\/p>\n\n\n\n
                \n\n\n\n
                Option B: Install Knative Serving from CLI<\/h2>\n\n\n\n
                Create the knative-serving<\/code> namespace and KnativeServing<\/code> resource:<\/p>\n\n\n
                cat <<'EOF'<\/span> > knative-serving.yaml\napiVersion<\/span>: v1\nkind<\/span>: Namespace\nmetadata<\/span>:\n  name: knative-serving\n---\napiVersion: operator.knative.dev\/v1beta1\nkind<\/span>: KnativeServing\nmetadata<\/span>:\n  name: knative-serving\n  namespace<\/span>: knative-serving\nEOF\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                Apply it:<\/p>\n\n\n
                oc<\/span> apply<\/span> -f<\/span> knative-serving<\/span>.yaml<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                Verify the custom resource:<\/p>\n\n\n
                oc<\/span> get<\/span> knativeserving<\/span>.operator<\/span>.knative<\/span>.dev<\/span> knative-serving<\/span> -n<\/span> knative-serving<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                Check Knative Serving conditions:<\/p>\n\n\n
                oc get knativeserving.operator.knative.dev knative-serving -n knative-serving \\\n  --template='{{range .status.conditions}}{{printf \"%s=%s\\n\" .type .status}}{{end}}'<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                Expected result should show conditions with:<\/p>\n\n\n
                True<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                Check pods:<\/p>\n\n\n
                oc get<\/span> pods -n knative-serving\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                You should see Knative Serving pods running.<\/p>\n\n\n\n
                Example components may include:<\/p>\n\n\n
                activator\nautoscaler\ncontroller\nwebhook\n<\/code><\/span><\/pre>\n\n\n
                The exact pod names can vary by OpenShift Serverless version.<\/p>\n\n\n\n
                \n\n\n\n
                Part 6: Validate Serverless Installation<\/h1>\n\n\n\n
                Run:<\/p>\n\n\n
                oc api-resources | grep -i knative\n<\/code><\/span><\/pre>\n\n\n
                Check for Knative Service API:<\/p>\n\n\n
                oc api-resources | grep ksvc\n<\/code><\/span><\/pre>\n\n\n
                Expected result should include:<\/p>\n\n\n
                services<\/span>   ksvc<\/span>   serving<\/span>.knative<\/span>.dev<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                Check Knative Serving namespace:<\/p>\n\n\n
                oc get<\/span> pods -n knative-serving\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                Check OpenShift Serverless namespace:<\/p>\n\n\n
                oc get<\/span> pods -n openshift-serverless\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                If the Operator and Knative Serving pods are running, the platform setup is ready.<\/p>\n\n\n\n
                \n\n\n\n
                Part 7: Install and Validate the kn<\/code> CLI<\/h1>\n\n\n\n
                The kn<\/code> CLI is the Knative command-line tool.<\/p>\n\n\n\n
                It is required for the kn func<\/code> workflow.<\/p>\n\n\n\n
                Install from Web Console<\/h2>\n\n\n\n
                  \n
                1. Open the OpenShift web console.<\/li>\n\n\n\n
                2. Click the ?<\/strong> icon in the upper-right corner.<\/li>\n\n\n\n
                3. Click Command Line Tools<\/strong>.<\/li>\n\n\n\n
                4. Download the Knative CLI for your operating system.<\/li>\n\n\n\n
                5. Extract the archive.<\/li>\n\n\n\n
                6. Move the kn<\/code> binary into a directory on your PATH<\/code>.<\/li>\n<\/ol>\n\n\n\n
                  On Linux or macOS, a typical location is:<\/p>\n\n\n
                  \/usr\/local\/bin\n<\/code><\/span><\/pre>\n\n\n
                  On Windows, put kn.exe<\/code> in a folder included in your PATH<\/code>.<\/p>\n\n\n\n
                  \n\n\n\n
                  Validate kn<\/code><\/h2>\n\n\n\n
                  Run:<\/p>\n\n\n
                  kn version\n<\/code><\/span><\/pre>\n\n\n
                  Check that the function commands are available:<\/p>\n\n\n
                  kn func --help\n<\/code><\/span><\/pre>\n\n\n
                  Expected result:<\/p>\n\n\n
                  Available Commands:\n  build\n  create\n  deploy\n  invoke\n  run\n  delete<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  The exact output may vary, but kn func<\/code> should be recognized.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 8: Validate Podman or Docker<\/h1>\n\n\n\n
                  OpenShift Serverless Functions need a local container engine to build function images.<\/p>\n\n\n\n
                  Podman is recommended for this lab.<\/p>\n\n\n\n
                  Check Podman:<\/p>\n\n\n
                  podman version\n<\/code><\/span><\/pre>\n\n\n
                  If you use Docker instead:<\/p>\n\n\n
                  docker version\n<\/code><\/span><\/pre>\n\n\n
                  For macOS or Windows with Podman, make sure the Podman machine is running:<\/p>\n\n\n
                  podman machine list<\/span>\npodman machine start\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                  If Podman or Docker is not working, kn func deploy<\/code> will fail during the build step.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 9: Prepare an Image Registry<\/h1>\n\n\n\n
                  When you deploy a function, the function image must be pushed to a container image registry.<\/p>\n\n\n\n
                  You have two options:<\/p>\n\n\n\n
                  Option<\/th>Best For<\/th><\/tr><\/thead>
                  OpenShift internal registry<\/td>Local OpenShift lab<\/td><\/tr>
                  Quay.io or another external registry<\/td>Real team workflow or if internal registry is difficult<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                  For OpenShift Local classroom labs, use the OpenShift internal registry.<\/p>\n\n\n\n
                  \n\n\n\n
                  Option A: Use OpenShift Internal Registry<\/h2>\n\n\n\n
                  Log in as kubeadmin<\/code>:<\/p>\n\n\n
                  oc login -u kubeadmin https:\/\/api.crc.testing:6443<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Expose the default OpenShift image registry route:<\/p>\n\n\n
                  oc patch configs.imageregistry.operator.openshift.io\/cluster \\\n  --type=merge \\\n  -p '{\"spec\":{\"defaultRoute\":true}}'<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Wait for the default registry route:<\/p>\n\n\n
                  oc get<\/span> route default-route -n openshift-image-registry\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Save the registry hostname:<\/p>\n\n\n
                  REGISTRY_HOST=$(oc get route default<\/span>-route -n openshift-image-registry -o jsonpath='{.spec.host}'<\/span>)\necho<\/span> \"$REGISTRY_HOST\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Log in to the registry with Podman:<\/p>\n\n\n
                  podman login --tls-verify=false<\/span> \\\n  -u \"$(oc whoami)\"<\/span> \\\n  -p \"$(oc whoami -t)\"<\/span> \\\n  \"$REGISTRY_HOST\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  If login succeeds, you are ready to push function images to the internal registry.<\/p>\n\n\n\n
                  \n\n\n\n
                  Option B: Use Quay.io<\/h2>\n\n\n\n
                  Use this option only if the OpenShift internal registry route does not work in your local environment.<\/p>\n\n\n\n
                  Log in to Quay.io:<\/p>\n\n\n
                  podman<\/span> login<\/span> quay<\/span>.io<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                  When deploying the function later, use an image name such as:<\/p>\n\n\n
                  quay.io\/<your-quay-username<\/span>><\/span>\/lab14-hello-func:latest\n<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Replace <your-quay-username><\/code> with your actual Quay username.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 10: Create a Student Project<\/h1>\n\n\n\n
                  Log in as developer<\/code>:<\/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
                  Create a new project:<\/p>\n\n\n
                  oc new<\/span>-project lab14-serverless-functions\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 \"lab14-serverless-functions\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  \n\n\n\n
                  Part 11: Create a Node.js Serverless Function<\/h1>\n\n\n\n
                  Create a function:<\/p>\n\n\n
                  kn func create -l node -t http lab14-hello-func\n<\/code><\/span><\/pre>\n\n\n
                  Expected output:<\/p>\n\n\n
                  Created node function<\/span> in<\/span> lab14<\/span>-hello<\/span>-func<\/span>\n<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Go into the function directory:<\/p>\n\n\n
                  cd lab14-hello-func\n<\/code><\/span><\/pre>\n\n\n
                  List the files:<\/p>\n\n\n
                  ls -la\n<\/code><\/span><\/pre>\n\n\n
                  Expected files include:<\/p>\n\n\n
                  func<\/span>.yaml<\/span>\nindex<\/span>.js<\/span>\npackage<\/span>.json<\/span>\nREADME<\/span>.md<\/span>\ntest<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                  \n\n\n\n
                  Part 12: Understand the Function Project<\/h1>\n\n\n\n
                  The function project contains:<\/p>\n\n\n\n
                  File or Directory<\/th>Purpose<\/th><\/tr><\/thead>
                  func.yaml<\/code><\/td>Function configuration<\/td><\/tr>
                  index.js<\/code><\/td>Function source code<\/td><\/tr>
                  package.json<\/code><\/td>Node.js dependencies and scripts<\/td><\/tr>
                  README.md<\/code><\/td>Function documentation<\/td><\/tr>
                  test\/<\/code><\/td>Unit and integration tests<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                  The most important files for this beginner lab are:<\/p>\n\n\n
                  func<\/span>.yaml<\/span>\nindex<\/span>.js<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                  \n\n\n\n
                  Part 13: Replace the Function Code<\/h1>\n\n\n\n
                  Open index.js<\/code> and replace the content with the following code.<\/p>\n\n\n
                  cat <<'EOF'<\/span> > index.js\nconst<\/span> Function<\/span> = {\n  handle<\/span>: (context, body<\/span>) =><\/span> {\n    context.log.info('Lab 14 function was invoked'<\/span>);\n\n    return<\/span> 'Hello from OpenShift Serverless Functions - Lab 14'<\/span>;\n  }\n};\n\nmodule<\/span>.exports = Function<\/span>;\nEOF\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  This function returns a simple text response.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 14: Review func.yaml<\/code><\/h1>\n\n\n\n
                  View the function configuration:<\/p>\n\n\n
                  cat<\/span> func<\/span>.yaml<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                  You should see values such as:<\/p>\n\n\n
                  name<\/span>: lab14-hello-func\nruntime<\/span>: node\n<\/code><\/span>Code language:<\/span> HTTP<\/span> (<\/span>http<\/span>)<\/span><\/small><\/pre>\n\n\n
                  The exact content may vary depending on your kn<\/code> version.<\/p>\n\n\n\n
                  Do not manually change the file unless your instructor asks you to.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 15: Optional Local Run<\/h1>\n\n\n\n
                  You can run the function locally before deploying it.<\/p>\n\n\n\n
                  This step requires Podman or Docker to work correctly.<\/p>\n\n\n\n
                  Run:<\/p>\n\n\n
                  kn func run\n<\/code><\/span><\/pre>\n\n\n
                  Open a second terminal and go into the same function directory:<\/p>\n\n\n
                  cd lab14-hello-func\n<\/code><\/span><\/pre>\n\n\n
                  Invoke the local function:<\/p>\n\n\n
                  kn func invoke\n<\/code><\/span><\/pre>\n\n\n
                  Expected response:<\/p>\n\n\n
                  Hello from<\/span> OpenShift Serverless Functions - Lab 14<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Stop the local function by pressing:<\/p>\n\n\n
                  Ctrl + C\n<\/code><\/span><\/pre>\n\n\n
                  If local run does not work because of Podman or Docker networking, continue with cluster deployment.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 16: Deploy the Function to OpenShift<\/h1>\n\n\n\n
                  Make sure you are in the function directory:<\/p>\n\n\n
                  pwd\n<\/code><\/span><\/pre>\n\n\n
                  Expected path should end with:<\/p>\n\n\n
                  lab14-hello-func\n<\/code><\/span><\/pre>\n\n\n
                  Set the project:<\/p>\n\n\n
                  oc project lab14-serverless-functions\n<\/code><\/span><\/pre>\n\n\n
                  Get the internal registry hostname if you are using the OpenShift internal registry:<\/p>\n\n\n
                  REGISTRY_HOST=$(oc get route default<\/span>-route -n openshift-image-registry -o jsonpath='{.spec.host}'<\/span>)\necho<\/span> \"$REGISTRY_HOST\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Deploy the function:<\/p>\n\n\n
                  kn func deploy -i \"$REGISTRY_HOST\/lab14-serverless-functions\/lab14-hello-func:latest\"<\/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
                  Function<\/span> deployed at:\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  This command builds the function image, pushes it to the image registry, and deploys it as a Knative Service.<\/p>\n\n\n\n
                  \n\n\n\n
                  Quay.io Alternative<\/h2>\n\n\n\n
                  If you are using Quay.io instead of the OpenShift internal registry, run:<\/p>\n\n\n
                  kn func deploy -i \"quay.io\/<your-quay-username<\/span>><\/span>\/lab14-hello-func:latest\"\n<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Replace <your-quay-username><\/code> with your actual Quay username.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 17: Verify the Function Deployment<\/h1>\n\n\n\n
                  Check Knative Services:<\/p>\n\n\n
                  oc get<\/span> ksvc\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Expected output:<\/p>\n\n\n
                  NAME                 URL                                      LATESTCREATED              LATESTREADY                READY\nlab14-hello-func     http:\/\/lab14-hello-func-...              lab14-hello-func-00001     lab14-hello-func-00001     True<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Check with kn<\/code>:<\/p>\n\n\n
                  kn service list<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Expected result should include:<\/p>\n\n\n
                  lab14-hello-func\n<\/code><\/span><\/pre>\n\n\n
                  Check all related Knative resources:<\/p>\n\n\n
                  oc<\/span> get<\/span> ksvc<\/span>,revision<\/span>,configuration<\/span>,routes<\/span>.serving<\/span>.knative<\/span>.dev<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                  You should see resources related to:<\/p>\n\n\n
                  lab14-hello-func\n<\/code><\/span><\/pre>\n\n\n
                  \n\n\n\n
                  Part 18: Get the Function URL<\/h1>\n\n\n\n
                  Get the function URL:<\/p>\n\n\n
                  FUNC_URL=$(oc get ksvc lab14-hello-func -o jsonpath='{.status.url}'<\/span>)\necho<\/span> \"$FUNC_URL\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Expected output:<\/p>\n\n\n
                  http:\/\/lab14-hello-func-lab14-serverless-functions.apps-crc.testing<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  The exact hostname may be different.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 19: Invoke the Function<\/h1>\n\n\n\n
                  Invoke using kn func<\/code>:<\/p>\n\n\n
                  kn func invoke\n<\/code><\/span><\/pre>\n\n\n
                  Expected response:<\/p>\n\n\n
                  Hello from<\/span> OpenShift Serverless Functions - Lab 14<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Invoke using curl<\/code>:<\/p>\n\n\n
                  curl -s \"$FUNC_URL\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Expected response:<\/p>\n\n\n
                  Hello from<\/span> OpenShift Serverless Functions - Lab 14<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  If the first request is slow, that can be normal. A scaled-to-zero function may need a few seconds to start.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 20: View Function Logs<\/h1>\n\n\n\n
                  Check the Knative Service:<\/p>\n\n\n
                  oc get<\/span> ksvc lab14-hello-func\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/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
                  View logs from the function pod:<\/p>\n\n\n
                  oc logs -l serving.knative.dev\/service=lab14-hello-func\n<\/code><\/span><\/pre>\n\n\n
                  Expected log message:<\/p>\n\n\n
                  Lab 14<\/span> function<\/span> was<\/span> invoked<\/span>\n<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  If no pod exists because the function scaled to zero, invoke the function again:<\/p>\n\n\n
                  curl -s \"$FUNC_URL\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Then check logs again:<\/p>\n\n\n
                  oc logs -l serving.knative.dev\/service=lab14-hello-func\n<\/code><\/span><\/pre>\n\n\n
                  \n\n\n\n
                  Part 21: Observe Scale-to-Zero<\/h1>\n\n\n\n
                  Knative Serving can scale a function down to zero pods when it is idle.<\/p>\n\n\n\n
                  Run:<\/p>\n\n\n
                  oc get<\/span> pods -l serving.knative.dev\/service=lab14-hello-func\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  You should see a running pod shortly after invoking the function.<\/p>\n\n\n\n
                  Now wait for a short idle period.<\/p>\n\n\n\n
                  Run the command again:<\/p>\n\n\n
                  oc get<\/span> pods -l serving.knative.dev\/service=lab14-hello-func\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  After the function has been idle, the pod may disappear.<\/p>\n\n\n\n
                  Expected result after scale-to-zero:<\/p>\n\n\n
                  No resources found\n<\/code><\/span><\/pre>\n\n\n
                  The exact time can vary based on cluster configuration.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 22: Observe Scale-from-Zero<\/h1>\n\n\n\n
                  Invoke the function again:<\/p>\n\n\n
                  curl -s \"$FUNC_URL\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Expected response:<\/p>\n\n\n
                  Hello from<\/span> OpenShift Serverless Functions - Lab 14<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Immediately check pods:<\/p>\n\n\n
                  oc get<\/span> pods -l serving.knative.dev\/service=lab14-hello-func\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  You should see a new pod created for the function.<\/p>\n\n\n\n
                  This proves that the function can scale from zero when traffic arrives.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 23: Inspect the Knative Service<\/h1>\n\n\n\n
                  Describe the Knative Service:<\/p>\n\n\n
                  oc describe ksvc lab14-hello-func\n<\/code><\/span><\/pre>\n\n\n
                  Look for:<\/p>\n\n\n
                  URL\nLatestCreatedRevisionName\nLatestReadyRevisionName\nReady\nRoutesReady\nConfigurationsReady\n<\/code><\/span><\/pre>\n\n\n
                  Check the latest revision:<\/p>\n\n\n
                  oc get<\/span> revision\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Check the Knative configuration:<\/p>\n\n\n
                  oc get<\/span> configuration\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Check the Knative route:<\/p>\n\n\n
                  oc<\/span> get<\/span> routes<\/span>.serving<\/span>.knative<\/span>.dev<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                  These resources are created and managed by Knative Serving.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 24: Update the Function<\/h1>\n\n\n\n
                  Modify the function response:<\/p>\n\n\n
                  cat <<'EOF'<\/span> > index.js\nconst<\/span> Function<\/span> = {\n  handle<\/span>: (context, body<\/span>) =><\/span> {\n    context.log.info('Lab 14 function version 2 was invoked'<\/span>);\n\n    return<\/span> 'Hello from OpenShift Serverless Functions - Lab 14 - Version 2'<\/span>;\n  }\n};\n\nmodule<\/span>.exports = Function<\/span>;\nEOF\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Deploy again:<\/p>\n\n\n
                  kn func deploy -i \"$REGISTRY_HOST\/lab14-serverless-functions\/lab14-hello-func:latest\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Invoke the function:<\/p>\n\n\n
                  curl -s \"$FUNC_URL\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Expected response:<\/p>\n\n\n
                  Hello from<\/span> OpenShift Serverless Functions - Lab 14<\/span> - Version 2<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  Check revisions:<\/p>\n\n\n
                  oc get<\/span> revision\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                  You should see more than one revision.<\/p>\n\n\n\n
                  This shows that updating a function creates a new Knative revision.<\/p>\n\n\n\n
                  \n\n\n\n
                  Part 25: Validate from the Web Console<\/h1>\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. Select project:<\/li>\n<\/ol>\n\n\n
                    lab14-serverless-functions\n<\/code><\/span><\/pre>\n\n\n
                      \n
                    1. Switch to Developer<\/strong> perspective.<\/li>\n\n\n\n
                    2. Go to Topology<\/strong>.<\/li>\n\n\n\n
                    3. You should see:<\/li>\n<\/ol>\n\n\n
                      lab14-hello-func\n<\/code><\/span><\/pre>\n\n\n
                        \n
                      1. Click the function.<\/li>\n\n\n\n
                      2. Check the Resources<\/strong> tab.<\/li>\n\n\n\n
                      3. Check pods, revisions, and routes if shown.<\/li>\n\n\n\n
                      4. Open the function URL from the console if available.<\/li>\n<\/ol>\n\n\n\n
                        The web console layout can vary by OpenShift version, but the function should be visible as a serverless workload.<\/p>\n\n\n\n
                        \n\n\n\n
                        Part 26: Full Student Validation Script<\/h1>\n\n\n\n
                        Run this from the function directory:<\/p>\n\n\n
                        oc project lab14-serverless-functions\n\necho<\/span> \"Checking Knative Service...\"<\/span>\noc get ksvc lab14-hello-func\n\necho<\/span> \"Checking URL...\"<\/span>\nFUNC_URL=$(oc get ksvc lab14-hello-func -o jsonpath='{.status.url}'<\/span>)\necho<\/span> \"$FUNC_URL\"<\/span>\n\necho<\/span> \"Invoking function...\"<\/span>\ncurl -s \"$FUNC_URL\"<\/span>\necho<\/span>\n\necho<\/span> \"Checking Knative resources...\"<\/span>\noc get ksvc,revision,configuration,routes.serving.knative.dev\n\necho<\/span> \"Checking pods...\"<\/span>\noc get pods -l serving.knative.dev\/service=lab14-hello-func\n\necho<\/span> \"Checking logs...\"<\/span>\noc logs -l serving.knative.dev\/service=lab14-hello-func --tail=50<\/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. Knative Service exists.<\/li>\n\n\n\n
                        2. Function URL exists.<\/li>\n\n\n\n
                        3. Function returns a response.<\/li>\n\n\n\n
                        4. Revision exists.<\/li>\n\n\n\n
                        5. Configuration exists.<\/li>\n\n\n\n
                        6. Knative Route exists.<\/li>\n\n\n\n
                        7. Pod exists after invocation.<\/li>\n\n\n\n
                        8. Logs show invocation output.<\/li>\n<\/ol>\n\n\n\n
                          \n\n\n\n
                          Part 27: Troubleshooting<\/h1>\n\n\n\n
                          Problem 1: kn: command not found<\/code><\/h2>\n\n\n\n
                          Cause<\/h3>\n\n\n\n
                          The Knative CLI is not installed or not in your PATH<\/code>.<\/p>\n\n\n\n
                          Fix<\/h3>\n\n\n\n
                          Download kn<\/code> from:<\/p>\n\n\n
                          OpenShift web console<\/span> > ? > Command Line Tools\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                          Move the binary to a directory in your PATH<\/code>.<\/p>\n\n\n\n
                          Verify:<\/p>\n\n\n
                          kn version\n<\/code><\/span><\/pre>\n\n\n
                          \n\n\n\n
                          Problem 2: kn func<\/code> Is Not Recognized<\/h2>\n\n\n\n
                          Cause<\/h3>\n\n\n\n
                          You may have an older or incorrect kn<\/code> binary.<\/p>\n\n\n\n
                          Fix<\/h3>\n\n\n\n
                          Install the kn<\/code> CLI version provided by your OpenShift Serverless installation.<\/p>\n\n\n\n
                          Check:<\/p>\n\n\n
                          kn func --help\n<\/code><\/span><\/pre>\n\n\n
                          If this fails, reinstall the CLI from the OpenShift web console Command Line Tools page.<\/p>\n\n\n\n
                          \n\n\n\n
                          Problem 3: OpenShift Serverless Operator Is Not Installed<\/h2>\n\n\n\n
                          Symptom<\/h3>\n\n\n
                          oc get<\/span> pods -n openshift-serverless\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                          fails or shows no serverless operator pods.<\/p>\n\n\n\n
                          Fix<\/h3>\n\n\n\n
                          Install the OpenShift Serverless Operator using OperatorHub or the CLI YAML from this lab.<\/p>\n\n\n\n
                          Verify:<\/p>\n\n\n
                          oc get<\/span> csv -n openshift-serverless\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                          Expected phase:<\/p>\n\n\n
                          Succeeded\n<\/code><\/span><\/pre>\n\n\n
                          \n\n\n\n
                          Problem 4: Knative Serving Is Missing<\/h2>\n\n\n\n
                          Symptom<\/h3>\n\n\n
                          oc get<\/span> ksvc\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                          returns an error such as:<\/p>\n\n\n
                          the server doesn't have a resource type \"ksvc\"\n<\/code><\/span><\/pre>\n\n\n
                          Cause<\/h3>\n\n\n\n
                          Knative Serving is not installed.<\/p>\n\n\n\n
                          Fix<\/h3>\n\n\n\n
                          Create the KnativeServing<\/code> resource:<\/p>\n\n\n
                          oc<\/span> apply<\/span> -f<\/span> knative-serving<\/span>.yaml<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                          Verify:<\/p>\n\n\n
                          oc get<\/span> pods -n knative-serving\noc api-resources | grep ksvc\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                          \n\n\n\n
                          Problem 5: Function Build Fails<\/h2>\n\n\n\n
                          Possible Causes<\/h3>\n\n\n\n
                            \n
                          1. Podman or Docker is not running.<\/li>\n\n\n\n
                          2. Image registry login failed.<\/li>\n\n\n\n
                          3. Registry route is not exposed.<\/li>\n\n\n\n
                          4. TLS verification failed.<\/li>\n\n\n\n
                          5. Laptop does not have enough CPU or memory.<\/li>\n\n\n\n
                          6. Network\/VPN blocks registry access.<\/li>\n<\/ol>\n\n\n\n
                            Check<\/h3>\n\n\n
                            podman version\npodman info\n<\/code><\/span><\/pre>\n\n\n
                            Check registry route:<\/p>\n\n\n
                            oc get<\/span> route default-route -n openshift-image-registry\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Check registry login:<\/p>\n\n\n
                            REGISTRY_HOST=$(oc get route default<\/span>-route -n openshift-image-registry -o jsonpath='{.spec.host}'<\/span>)\n\npodman login --tls-verify=false<\/span> \\\n  -u \"$(oc whoami)\"<\/span> \\\n  -p \"$(oc whoami -t)\"<\/span> \\\n  \"$REGISTRY_HOST\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Try deploy again:<\/p>\n\n\n
                            kn func deploy -i \"$REGISTRY_HOST\/lab14-serverless-functions\/lab14-hello-func:latest\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            \n\n\n\n
                            Problem 6: Function Deploy Fails with Registry Push Error<\/h2>\n\n\n\n
                            Cause<\/h3>\n\n\n\n
                            The function image cannot be pushed to the registry.<\/p>\n\n\n\n
                            Fix Option 1: Re-login to OpenShift Registry<\/h3>\n\n\n
                            REGISTRY_HOST=$(oc get route default<\/span>-route -n openshift-image-registry -o jsonpath='{.spec.host}'<\/span>)\n\npodman login --tls-verify=false<\/span> \\\n  -u \"$(oc whoami)\"<\/span> \\\n  -p \"$(oc whoami -t)\"<\/span> \\\n  \"$REGISTRY_HOST\"<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Deploy again:<\/p>\n\n\n
                            kn func deploy -i \"$REGISTRY_HOST\/lab14-serverless-functions\/lab14-hello-func:latest\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Fix Option 2: Use Quay.io<\/h3>\n\n\n
                            podman login quay.io\nkn func deploy -i \"quay.io\/<your-quay-username<\/span>><\/span>\/lab14-hello-func:latest\"\n<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
                            \n\n\n\n
                            Problem 7: Function URL Does Not Open<\/h2>\n\n\n\n
                            Check<\/h3>\n\n\n
                            oc get<\/span> ksvc lab14-hello-func\noc describe ksvc lab14-hello-func\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Check URL:<\/p>\n\n\n
                            oc get ksvc lab14-hello-func -o jsonpath='{.status.url}'<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Check Knative route:<\/p>\n\n\n
                            oc<\/span> get<\/span> routes<\/span>.serving<\/span>.knative<\/span>.dev<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/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
                            Invoke again:<\/p>\n\n\n
                            curl -v \"$FUNC_URL\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            If DNS fails on your laptop, check CRC status:<\/p>\n\n\n
                            crc status\n<\/code><\/span><\/pre>\n\n\n
                            \n\n\n\n
                            Problem 8: Function Returns Slowly on First Request<\/h2>\n\n\n\n
                            This can be normal.<\/p>\n\n\n\n
                            If the function scaled to zero, the first request must start a new pod.<\/p>\n\n\n\n
                            This is called:<\/p>\n\n\n
                            scale-from<\/span>-zero\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Second and later requests are usually faster while the pod is still running.<\/p>\n\n\n\n
                            \n\n\n\n
                            Problem 9: No Function Pod Is Running<\/h2>\n\n\n\n
                            This may be normal if the function scaled to zero.<\/p>\n\n\n\n
                            Invoke the function:<\/p>\n\n\n
                            curl -s \"$FUNC_URL\"<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Then check pods immediately:<\/p>\n\n\n
                            oc get<\/span> pods -l serving.knative.dev\/service=lab14-hello-func\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            \n\n\n\n
                            Problem 10: Web Console Function Creation Is Not Available<\/h2>\n\n\n\n
                            The web console function workflow requires additional setup, including OpenShift Pipelines and function pipeline tasks.<\/p>\n\n\n\n
                            For this lab, use the CLI workflow with:<\/p>\n\n\n
                            kn func create\nkn func deploy\nkn func invoke\n<\/code><\/span><\/pre>\n\n\n
                            This is simpler and more reliable for beginner students.<\/p>\n\n\n\n
                            \n\n\n\n
                            Part 28: Cleanup Student Resources<\/h1>\n\n\n\n
                            Delete the function:<\/p>\n\n\n
                            oc delete<\/span> ksvc lab14-hello-func\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Or, from the function directory:<\/p>\n\n\n
                            kn func delete<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Delete the project:<\/p>\n\n\n
                            oc delete<\/span> project lab14-serverless-functions\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 lab14-serverless-functions\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Expected result:<\/p>\n\n\n
                            NotFound\n<\/code><\/span><\/pre>\n\n\n
                            \n\n\n\n
                            Part 29: Optional Admin Cleanup<\/h1>\n\n\n\n
                            Only run this if the OpenShift Local cluster is used only for this lab.<\/p>\n\n\n\n
                            Do not remove shared Serverless components from a classroom cluster unless the instructor confirms.<\/p>\n\n\n\n
                            Log in as kubeadmin<\/code>:<\/p>\n\n\n
                            oc login -u kubeadmin https:\/\/api.crc.testing:6443<\/span>\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Delete Knative Serving:<\/p>\n\n\n
                            oc<\/span> delete<\/span> knativeserving<\/span>.operator<\/span>.knative<\/span>.dev<\/span> knative-serving<\/span> -n<\/span> knative-serving<\/span>\n<\/code><\/span>Code language:<\/span> CSS<\/span> (<\/span>css<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Delete Knative Serving namespace:<\/p>\n\n\n
                            oc delete<\/span> namespace knative-serving\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Delete the Serverless Operator subscription:<\/p>\n\n\n
                            oc delete<\/span> subscription serverless-operator -n openshift-serverless\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            List CSVs:<\/p>\n\n\n
                            oc get<\/span> csv -n openshift-serverless\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Delete the Serverless CSV shown in the output if required:<\/p>\n\n\n
                            oc delete csv <serverless-csv-name<\/span>><\/span> -n openshift-serverless\n<\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
                            Delete the Serverless namespace:<\/p>\n\n\n
                            oc delete<\/span> namespace openshift-serverless\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 installed and used OpenShift Serverless Functions.<\/p>\n\n\n\n
                            You created:<\/p>\n\n\n\n
                            Resource<\/th>Purpose<\/th><\/tr><\/thead>
                            OpenShift Serverless Operator<\/td>Manages Knative components<\/td><\/tr>
                            KnativeServing<\/td>Installs Knative Serving<\/td><\/tr>
                            Project<\/td>Isolated namespace for the function<\/td><\/tr>
                            Function source<\/td>Node.js function code<\/td><\/tr>
                            Container image<\/td>Built function runtime image<\/td><\/tr>
                            Knative Service<\/td>Serverless runtime resource<\/td><\/tr>
                            Revision<\/td>Immutable version of the function<\/td><\/tr>
                            Configuration<\/td>Knative configuration state<\/td><\/tr>
                            Knative Route<\/td>Function URL routing<\/td><\/tr>
                            Pod<\/td>Runtime instance created when traffic arrives<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
                            You verified that:<\/p>\n\n\n\n
                              \n
                            1. OpenShift Serverless is installed.<\/li>\n\n\n\n
                            2. Knative Serving is running.<\/li>\n\n\n\n
                            3. kn func<\/code> can create functions.<\/li>\n\n\n\n
                            4. A Node.js function can be deployed.<\/li>\n\n\n\n
                            5. The function can be invoked by URL.<\/li>\n\n\n\n
                            6. The function can scale to zero.<\/li>\n\n\n\n
                            7. The function can scale from zero when traffic arrives.<\/li>\n\n\n\n
                            8. Updating the function creates a new revision.<\/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 OpenShift Serverless based on?<\/p>\n\n\n\n
                              Answer<\/h3>\n\n\n\n
                              Knative.<\/p>\n\n\n\n
                              \n\n\n\n
                              Question 2<\/h2>\n\n\n\n
                              Which OpenShift Serverless component is required to run functions?<\/p>\n\n\n\n
                              Answer<\/h3>\n\n\n\n
                              Knative Serving.<\/p>\n\n\n\n
                              \n\n\n\n
                              Question 3<\/h2>\n\n\n\n
                              Which CLI command creates a function?<\/p>\n\n\n\n
                              Answer<\/h3>\n\n\n
                              kn func create\n<\/code><\/span><\/pre>\n\n\n
                              \n\n\n\n
                              Question 4<\/h2>\n\n\n\n
                              Which CLI command deploys a function?<\/p>\n\n\n\n
                              Answer<\/h3>\n\n\n
                              kn func deploy\n<\/code><\/span><\/pre>\n\n\n
                              \n\n\n\n
                              Question 5<\/h2>\n\n\n\n
                              Which CLI command invokes a function?<\/p>\n\n\n\n
                              Answer<\/h3>\n\n\n
                              kn func invoke\n<\/code><\/span><\/pre>\n\n\n
                              \n\n\n\n
                              Question 6<\/h2>\n\n\n\n
                              What OpenShift resource is created when a function is deployed?<\/p>\n\n\n\n
                              Answer<\/h3>\n\n\n\n
                              A Knative Service.<\/p>\n\n\n\n
                              \n\n\n\n
                              Question 7<\/h2>\n\n\n\n
                              What command lists Knative Services?<\/p>\n\n\n\n
                              Answer<\/h3>\n\n\n
                              oc get<\/span> ksvc\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                              \n\n\n\n
                              Question 8<\/h2>\n\n\n\n
                              What is scale-to-zero?<\/p>\n\n\n\n
                              Answer<\/h3>\n\n\n\n
                              Scale-to-zero means the function pod is removed when the function is idle.<\/p>\n\n\n\n
                              \n\n\n\n
                              Question 9<\/h2>\n\n\n\n
                              What is scale-from-zero?<\/p>\n\n\n\n
                              Answer<\/h3>\n\n\n\n
                              Scale-from-zero means a new function pod is created automatically when a request arrives.<\/p>\n\n\n\n
                              \n\n\n\n
                              Question 10<\/h2>\n\n\n\n
                              Why does the first request sometimes take longer?<\/p>\n\n\n\n
                              Answer<\/h3>\n\n\n\n
                              Because the function may need to start from zero pods before it can serve the request.<\/p>\n\n\n\n
                              \n\n\n\n
                              Part 32: Instructor Notes<\/h1>\n\n\n\n
                              This lab intentionally uses the CLI-based kn func<\/code> workflow instead of the web-console function creation workflow.<\/p>\n\n\n\n
                              Reason:<\/p>\n\n\n\n
                              The web-console function workflow requires additional setup such as OpenShift Pipelines and function-specific pipeline tasks. That is useful for an advanced lab, but it adds too much complexity for a first serverless functions lab.<\/p>\n\n\n\n
                              Recommended follow-up labs:<\/p>\n\n\n\n
                                \n
                              1. Create functions from the OpenShift web console.<\/li>\n\n\n\n
                              2. Install OpenShift Pipelines for function builds.<\/li>\n\n\n\n
                              3. Connect an event source to a function.<\/li>\n\n\n\n
                              4. Use Knative Eventing.<\/li>\n\n\n\n
                              5. Trigger functions from Kafka.<\/li>\n\n\n\n
                              6. Configure function environment variables.<\/li>\n\n\n\n
                              7. Use ConfigMaps and Secrets with functions.<\/li>\n\n\n\n
                              8. Configure function concurrency.<\/li>\n\n\n\n
                              9. Configure autoscaling.<\/li>\n\n\n\n
                              10. Configure custom domains and TLS.<\/li>\n\n\n\n
                              11. Observe serverless metrics.<\/li>\n\n\n\n
                              12. Deploy Quarkus, Python, Go, and TypeScript functions.<\/li>\n\n\n\n
                              13. Deploy serverless applications using GitOps.<\/li>\n<\/ol>\n\n\n\n
                                \n\n\n\n
                                Part 33: 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
                                Validate Serverless Operator:<\/p>\n\n\n
                                oc get<\/span> csv -n openshift-serverless\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                Validate Knative Serving:<\/p>\n\n\n
                                oc get pods -n knative-serving\noc get knativeserving.operator.knative.dev knative-serving -n knative-serving \\\n  --template='{{range .status.conditions}}{{printf \"%s=%s\\n\" .type .status}}{{end}}'<\/span>\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
                                Validate CLI:<\/p>\n\n\n
                                kn version\nkn func --help\npodman version\n<\/code><\/span><\/pre>\n\n\n
                                Validate registry route:<\/p>\n\n\n
                                oc get<\/span> route default-route -n openshift-image-registry\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                Create a test function:<\/p>\n\n\n
                                oc new<\/span>-project lab14-validation\nkn func create -l node -t http lab14-test-func\ncd lab14-test-func\n\nREGISTRY_HOST=$(oc get route default<\/span>-route -n openshift-image-registry -o jsonpath='{.spec.host}'<\/span>)\n\nkn func deploy -i \"$REGISTRY_HOST\/lab14-validation\/lab14-test-func:latest\"<\/span>\n\nFUNC_URL=$(oc get ksvc lab14-test-func -o jsonpath='{.status.url}'<\/span>)\ncurl -s \"$FUNC_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
                                cd ..\noc delete<\/span> project lab14-validation\nrm -rf lab14-test-func\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                If the function deploys and responds successfully, 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 completed OpenShift Lab 14.<\/p>\n\n\n\n
                                You installed OpenShift Serverless, installed Knative Serving, created a Node.js serverless function, deployed it as a Knative Service, invoked it through a URL, checked the generated Knative resources, and observed serverless scale-to-zero behavior.<\/p>\n\n\n\n
                                The final workflow is:<\/p>\n\n\n
                                Function<\/span> source code\n  -> kn func build\/deploy\n  -> container image\n  -> Knative Service\n  -> Revision\n  -> Pod on demand\n  -> Function<\/span> URL\n  -> scale to zero when idle\n<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
                                This is one of the most important OpenShift developer workflows for event-driven and request-driven workloads.<\/p>\n","protected":false},"excerpt":{"rendered":"
                                Lab Objective In this lab, you will install and use OpenShift Serverless Functions on OpenShift Local. You will create a simple Node.js serverless function, deploy it to… <\/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-50040","post","type-post","status-publish","format-standard","hentry","category-openshift"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/50040","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=50040"}],"version-history":[{"count":4,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/50040\/revisions"}],"predecessor-version":[{"id":77172,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/50040\/revisions\/77172"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=50040"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=50040"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=50040"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}