Kubernetes SIG Service Catalog, 24 Feb 2017

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Service Catalog Basic Demo

Description

A demo of the service catalog API basics, showing adding a broker, creating a new instance of a service, and binding to that instance.

A

Hey everybody: it is Friday February, 24th 2017. My name is Paul from big Service Catalog and I'm, going to do a demo of our API server and controller working. That hopefully, will be interesting and kind of drive home from the concepts that you might have heard of talking. I heard us talking about in the Stig meetings and so forth. So here we go I'm going to share my screen.

A

Okay, so what I've got here is a local kubernetes cluster running I'm, using that local up cluster script in the kubernetes project to watch it and I have our Service Catalog API server, our Service Catalog controller.

A

Excuse me and a really simple service broker running in kubernetes, and so what I'm going to do is I'm going to create a broker resource for that that refers to.

A

Refers to this UPS broker, UPS insert user provided service in this case, and you can see here that the dis object. Spec has a URL that points to the in cluster DNS or the service could be neti service that fronts. This broker, so I'm going to go ahead and create it, and what we're going to see now is I just created this thing and then I got it back and there's a condition in the status that says that it's ready and the catalog has been fetched from this service broker.

A

So if I go and looking at the service classes, I.

A

Can see that there's this service class called user provided services or user provided service and let's take a look at that.

A

You can see it's got, one plan called default and it's provided by this ups broker.

A

So what I'm going to do now is I'm going to create a new instance.

A

That refers to that service class and, if I get that instance, we can see. Controller has already picked this up and asked the broker to provision a new instance of the service. For us. I service was ready, and that means that I can bind to it. So.

A

I'm going to, let's take a look at that with that finding looks like really quick.

A

It's pretty simple, it just says I, my name is UPS binding I exist in namespace test. Ns I refer to an instance called UPS instance, which we just created that exists in my namespace and I. Want you to put the results of the binding into a secret in my namespace called my secret. So.

A

What we're going to see on this broker give us back is just something like made-up credentials that don't really have any meaning. They just exist to show us that the machinery is working, so I'm going to create this.

A

Alright, let's take a look all right, so controllers already contacted the broker, told it to do a bye and gotten a payload back and injected that into my kubernetes namespace.

A

So let's take a look at the secrets in this namespace all right. There we go. We got my secret ah and, let's take a look at this thing, all right, the exact the data. The secret data in here is special key. One I am special key to so. This is. uh This is pretty much a very short made-up example of what the flow for the API is. If anybody has watched the Service, Catalog basics video- hopefully this new video that I'm recording now I am a demo dovetail nicely with that and illustrate the concepts.

A

So thanks a lot everybody and thanks a lot to everybody, who's contributed in Service Catalog. This has been a team effort and a really great learning experience for me. Working with so many folks that are new to kubernetes, alright see you out there in internet land. Soon everybody.