Would you like to run functions in your own Kubernetes clusters? Would you like it to be as simple as possible? How about providing Functions As a Service (FaaS) flavor of serverless computing to everyone in your company? If the answer to any of those questions is yes, you might want to explore Knative Functions.
Continue reading
This text was taken from the book and a Udemy course The DevOps Toolkit: Catalog, Patterns, And Blueprints
All the commands from this article are in the [04-03-knative.sh](Gist with the commands: https://gist.github.com/dc4ba562328c1d088047884026371f1f) Gist.
Before we dive into the actual usage of Knative, let’s see which components we got and how they interact with each other. We’ll approach the subject by trying to figure out the flow of a request. It starts with a user.
This time I will not write a lenghtly post. Instead, I’ll try to explain different deployment strategies through diagrams. This is for all those who dislike black and white terminal and prefer colors, boxes, and lines with arrows.
The deployment strategies are not presented in any particular order.
Serverless deployments are gaining traction. Today, we have quite a few choices for converting our applications into serverless inside Kubernetes cluster. One of those, my favorite, is Knative. We’ll explore how we can combine it with Jenkins X to create a fully automated continuous deployment pipeline that deploys serverless applications.
Jenkins X itself is serverless. That helps with many things, with better resource utilization and scalability being only a few of the benefits. Can we do something similar with our applications? Can we scale them to zero when no one is using them? Can we scale them up when the number of concurrent requests increases? Can we make our applications serverless?
Technology Conversations 