Cloud Native Computing Foundation KubeCon + CloudNativeCon Europe 2021, 15 May 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Sponsored Session: VMware - Automatically Turn Your Source Code into Scalable Microservices on Ku...

Description

Don’t miss out! Join us at our upcoming event: KubeCon + CloudNativeCon North America 2021 in Los Angeles, CA from October 12-15. Learn more at https://kubecon.io The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.

Sponsored Session: VMware - Automatically Turn Your Source Code into Scalable Microservices on Kubernetes

Speakers: Boskey Savla

Deploying and managing microservices on Kubernetes isn’t easy. You have to build the right dockerfile and container image and create various Kubernetes objects, like deployments, services, replicas, and horizontal pod autoscalers. And this is an iterative process with several testing and validation checkpoints along the way. Sound complex? It sure is.

In this demo, you’ll learn how to simplify and automate this with Cloud Native Buildpacks and Knative. Cloud Native Buildpacks figure out the language your code is written in, determine the best way to package the code, and build an OCI-compliant container image. And Knative takes that image and automatically generates the required configuration to create deployments, services, and automated pod scalers.

A

Hi meet sarah.

A

Sarah is a software developer working for an organization. Currently, she has a very difficult task at hand. Her business needs her and she is writing apps. That kind of solve her business challenges right now. She finally gets her act to work tests. It, and you know everything is working. Great sarah is excited.

A

All sarah wants to do now is just deploy the app see how it works. Maybe do some a b testing and get it going now in order to do so. Sarah first has to convert her code into a running container image where she can then deploy it on a platform. So she first has to start off by creating a docker file where she has to input kind of more of the runtime dependencies that her app needs.

A

uh What kind of language it is, etc and then, finally, she will build that application into a container image once she has done that she then has to deploy that onto kubernetes, but then she has to write a bunch of yaml understand what how kubernetes operates. You know create deployments, create services all of that stuff.

A

Now this can be very challenging and frustrating for sarah, because all she wants to do is test her app and see how it works out. Now, I'm going to introduce sarah to the k, kubernetes, k, native and k back combined together can help solve her problem.

A

How you ask, let's see how this works so the way to go about this would be if sarah could use build packs to actually automatically create container images and then use k-native that could be running on the same kubernetes cluster that she wants to deploy her apps to to actually build out scalable microservices.

A

These microservices could, you know, scale down to zero when there's no traffic or scale out as needed. So let's take a look at how this can be.

A

Done and for this demo we, I already have a kubernetes cluster deployed and um I am using octant, which is an open source tool to kind of view. What goes on within your kubernetes cluster. It's pretty neat um so for that cluster I already have cape bank deployed on it. uh Installing kpac is pretty easy.

A

Kpac is basically um a tool for consuming cloud-native build packs. So if you want to use cloud-native build packs, you could also use pack, which is a cli based command line tool that you could install on your laptop using home brew or something or even on any other machine, or you could consume things using cape back which actually gets deployed on a kubernetes cluster and for this purpose for the purpose of this demo, I'm actually going to use uh kpac.

A

I also have k native deployed over here on the same cluster. Again installing k-native is pretty standard. The documentation on their website covers that there's nothing going on over here, because we are not to get consuming k. Native now imagine sarah is actually working on an application called spring pet clinic. This is a very popular spring spring boot application, and um this is the repo that she's going to work on.

A

So this is what we'll be using as an example, and then we are going to use a docker hub as a way to you know, start publishing our images so to start off with we'll need um to build a very simple spec file for kpack.

A

So sarah has to just supply a very few details over here. For example, what does she want to call her image when it's once it's built?

A

What tags that she want to give that image the service account to use which has access to the um the repo that she's going to use, in my case, I'm going to use docker hub, so this service account actually understands how to get to docker hub and the credentials um for that and then which uh get url or where is my source code, so you know we are using spring pet clinic for the sample.

A

So here is this source code, where I want the m k back to build images based on that, so it's pretty standard. So let's go ahead and apply this.

A

So if you notice an opt-in, um you'll start seeing images being created, tutorial, image has started building and to look at what's going on, this build process might take a little bit, but if you want to see what's going on, you can actually, you know, load image logs for that, so you'll see what's going on in the back end over.

A

A

All right so looks like the build, has been successful and if we go and check our images over.

A

A

You'll see that this image is ready and it has actually been pushed to this particular um docker repo. So this is where image resides. So, if I log on to my docker hub account.

A

You'll see a new build was created just a minute ago, and it also has the latest tag.

A

All right so now that we have the you know, this is the way you know sarah could actually automate her image. Now we need to you know now. She still needs to push this image to kubernetes without having to write, um you know without having to worry about all the different objects needed to actually get her an addressable url. So that's where we'll be using uh k-nato.

A

Now we already have um the image name and mike I'm using the k native um cli to do so. So my canada is going to point to the kubernetes cluster where canada is installed, so the k n cli will talk to that api server and all I have to do is ask it to create a service.

A

Let's call it clinic and give it an image.

A

The image is just that we created or actually kpak built for us.

A

Okay, so pet clinic is ready and you can see the images created in uh if you go back to obtained and look at our canadian dashboard over here.

A

You'll see that you know the service called pet clinic was created. It already has a url that you know, k, native, went and created using kubernetes using ingress and all of the configurations needed.

A

uh You'll also see that you know there are pods that are now serving that particular application. At the same time, appropriate deployments, replica sets etc, have been created for that service and all of us all of this was completely automatic.

A

So now um just to take a look at their application. How it looks within kubernetes, all we have to do is: go click the url that k native created for us and there we go so pet clinic- is running within that kubernetes cluster. It already has a url and all the deployment properties taken care of automatically by k native.

A

So this is how using kpac or cloud native build packs and k-native survey. Sara could actually automate a lot of her tasks that she needs to do through a combination of k-native and cloud-native build packs. Thank you for watching this demo.