Using Serverless Deployments with Pull Requests
This lesson explains the benefits of using serverless deployments with pull requests and the steps to achieve it.
We'll cover the following...
- Benefits of using serverless deployments with pull requests
- Resource usage in preview environments
- Deployments initiated by pull requests
- 🔍 Databases in preview environments
- Creating a pull request
- Storing the name of the branch
- Checking activities
- Finding the name of the Namespace
- Checking Pods in the preview Namespace
- Figuring out the address
- Sending a request to the application
So far, all the changes we made were pushed to a branch. That was on purpose since one of my goals was to show you the benefits of using serverless deployments with pull requests.
Benefits of using serverless deployments with pull requests
The percentage of the apps running as serverless inevitably varies. Some might have all the stateless applications running as serverless, while others might have none. Between those two extremes can be all shades of gray. While I cannot tell you how many apps you should run as serverless deployments, what I can tell you with a high level of certainty is that you’ll use Knative much more in temporary environments like those created for pull requests than in permanent ones like staging and production. The reason for such a bold statement lies in the differences in purpose for running applications.