Creating a New Serverless Application Project
In this lesson, we will learn to create a new serverless application project.
We'll cover the following
- Creating a new quick start project
- Browsing to project directory
- Inspecting the values.yaml file
- Inspecting the templates directory
- Inspecting the ksvc.yaml file.
- Checking the activities of jx-knative
- Checking the activities of application deployed on staging
- Getting the Pods
- Describing the pods
- Getting all resources of the namespace jx-staging
- Querying ksvc to retrieve the domain
- Confirming if the application is working
- Reason for the slow response
- Checking the Pod
- Knative parameter configuration
- Checking for scale down
- Siege for testing parallel requests
- Running Siege and retrieving Pods
- Modifying the ksvc.yaml file
- Pushing the changes to Github and observing the activities
- Confirming the release deployed to staging
- Sending a request to the application
- Running Siege and retrieving pods related to the jx-knative
- Checking pods after some time
- How to prevent scaling down to zero replicas
Jenkins X does its best to be easy for everyone and not to introduce unnecessary complexity. True to that goal, there is nothing special users need to do to create a new project with serverless deployments. There is no additional command, nor are there any extra arguments. The jx edit deploy command already told Jenkins X that we want all new projects to be serverless by default, so all we have to do is create a new quick start.
Creating a new quick start project
Get hands-on with 1400+ tech skills courses.