Cloud Native Computing Foundation Cloud Native + Open Source Virtual Summit China 2020, 11 Sep 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Intro: Provider IBM Cloud - Sahdev Zala & Richard Theis, IBM

Description

Don’t miss out! Join us at our upcoming events: EnvoyCon Virtual on October 15 and KubeCon + CloudNativeCon North America 2020 Virtual from November 17-20. Learn more at https://kubecon.io The conferences feature presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.

Intro: Provider IBM Cloud - Sahdev Zala & Richard Theis, IBM

The Provider IBM Cloud is a subproject of the Cloud Provider SIG. In this session, the Provider IBM Cloud leads will provide an introduction of the project, and brief about the activities and GitHub repo on Kubernetes Cluster API Provider IBM Cloud. This will be followed by an overview of IBM Provider used by IBM Cloud Kubernetes Service (IKS) and Red Hat OpenShift on IBM Cloud, and how the provider leverages the Kubernetes Cloud Controller Manager. The session should be informative to anyone with interest in the Kubernetes Provider IBM Cloud subproject.

https://sched.co/cpAA

A

Nihao, my name is sadhu zala. I am a open source uh contributor developer at ibm and I contribute to kubernetes. I am a co-chair for this project called provider ibm cloud which is a sub project of kubernetes special interest group cloud provider, I'm also a maintainer for the hcd project.

A

uh Richard. Would you like to introduce yourself please.

B

Yeah I'm richard theis. I work on the ibm cloud, kubernetes service and red hat openshift and ibm cloud managed services, and also I uh co-chair of the provider ibm cloud working on primarily our cloud provider component for the ibm cloud. Kubernetes services.

A

Thank you richard, so welcome to this talk, uh the agenda. uh It's it's a it's a light agent. uh We'll talk more a lot more.

A

I think uh I will provide an overview of uh the sig club water uh and about this provider, ibm cloud sub project, uh the structure and activities and then talk a little bit about the cluster api provider, ibm cloud, which is um one of the git repository we have under this project and then we'll talk about ibm cloud provider, alrighty, so uh sig cloud provider is one of uh the special interest group in kubernetes. It owns. It owns the code uh for the cloud for interface and related work.

A

So, as you may know uh that for kubernetes to run on a provider-specific cloud, it needs certain functionalities uh that are provided by control loops. uh For example, you know uh for the node to find the zone and ip or load balancer uh related control loops.

A

So these control loops were part of the kubernetes core, but eventually the community thought it's good to decouple it from there. So that's where the cloud provider interface comes in picture.

A

It is now hosted on the github repository on its own on the cloud provider. Github repository and the cloudford interface is responsible for running all the cloud provider. Specific control loops.

A

Richard will talk more about uh uh architecture based on uh on this called ccm or cloud control manager, uh but for now uh continuing with cloud provider c, uh it also owns all the sub projects. uh They were formerly uh owned by uh different sigs. You know they were. There were like uh six uh uh uh dedicated uh sigs for different cloud provider, for example, ckws or c azure, or you know gcp or seek ibm cloud, and uh there were one for openstack and vmware as well.

A

So these are all now part of the sig cloud provider and they were there was some renaming as well and that renaming uh part of the renaming the project uh which was formerly known as sig ibm cloud, is now called provider ibm cloud, so the sig cloud provider also ensures ensures that uh the cubase ecosystem is evolving in a way that is neutral to cloud providers right. So I make sure that there is no such thing like favoring, one provider or another provider.

A

It also ensures that there is a consistent and high quality user experience across different providers as part of the sig policy.

A

uh The chair chairs of sigs, uh you know there is only one chair from a single company, so you know there can be two uh chairs or even three chairs sometime, but they make sure that they are representing different uh companies. You can find more about uh the about the sig uh and you know all the sub projects its owns uh under the github repository where you know it's under cuban this community uh get a pre uh get up uh reaper. So please take a look over there to learn more about the sig.

A

uh Alrighty, so the provider ibm cloud.

A

You know, as I said, it's a sub project of cloud provider sync and the purpose of this sub project is to build, deploy, maintain support and use kubernetes on ibm cloud.

A

So we have ibm cloud kubernetes service, uh which richard will talk later uh when he, when he talked about the ibm cloud provider- uh and he will talk about great at openshift commissioners as well.

A

uh So you know as a member of this sub project as a participant of this project, you, basically, you know, obviously get in touch with uh many developers and leaders from ibm uh who have uh work on building uh the ibm clouds, and you know, work on operating the ibm clouds right and you can follow the evaluation of the ibm cloud platforms uh with respect to kubernetes and related cnca projects. Right so this project is is, is is a platform to discuss things around kubernetes and related cnca projects.

A

You know and the repositories like I mentioned earlier, uh it is not a platform or a project to discuss any commercial uh product related discussions, or you know anything like that.

A

All right, the sick structure. uh You know there are three colleagues uh khalid amit who is uh ibm distinguished engineer, uh who leads the team on multi-cloud manager, uh richard thiess, uh who is representing ibm cloud kubernetes service and uh rocks, or radar openshift human resource and myself from the open source uh software development aside. uh I actually work with the cubase community uh on on different things.

A

um There is a main list, so you can be part of the main list and you know stay on top of uh any communication happening there. There is a slack disc discussions uh available on provider, dash, ibm cloud, slack channel uh it it's it's uh one of the channel on the kubernetes.com, so you know we would love to have you join there if you haven't participated uh before and if you're only participating participating there? Thank you. uh You know. We, we love you so much.

A

um You can learn more about the project uh again on the cloud provider page and the github cuban is community repo all right. So what are the different activities that we have uh as part of this subproject?

A

So we meet every month, so, every last wednesday of the month we have one hour meetings uh at 2 p.m. Eastern time we used to have weekly meetings, but starting this year we we changed it to monthly, because we have many other platforms discussions. As I mentioned slack meeting list emails. You know what not, uh if you're in different time zone, if you you know, if, if you can run the meetings, that is totally fine, we record uh all the meetings and all the recordings are made available uh on the kubernetes youtube channel.

A

So here is link. You can access the past recordings. There.

A

We also participate in the sig cloud provider, channel activities, of course, as a sub project of the sig. uh You know that's where we belong right uh and uh you know there are two uh main uh main. uh You know items uh as far as code is concerned. As far as you know, the real work is concerned.

A

uh We you know as part of this project.

A

uh I would like to mention uh the first one: is cluster api provider ibm cloud?

A

So, as you probably already know, there is a cluster api project in kubernetes. uh It basically brings declarative, kubernetes style apis to cluster creation, configuration and management, and uh you know the ibm cloud particular project that we we own under this sub project. It's basically an implementation of the uh cluster api project of kubernetes right. So, as I mentioned, uh it provides optional functionalities. On top of the core kubernetes to manage the cycle of a kubernetes cluster.

A

You can learn uh more about uh more about this sub project and uh the code at the github repository, which is on github.com kubernetes.6, and you know cluster api for driving cloud. So please uh visit there. uh Let us know if you any questions on the on the slack channel or mailing list or anything any by any domain.

A

The second thing is uh ibm cloud provider right, so uh the support for out of free ibm cloud provider is under progress internally, we already implement the ccm, as I mentioned earlier. The cloudwater interface you know enables that ccm architecture, so we already have that internally, but richard will talk more about the plan going forward uh with the ibm club provider. So with that uh richard to you thanks all right, very.

B

Good, thank you, so yeah I'll run at a high level here over the managed services and then how the cloud provider fits into those uh so we'll first start with our first service that we provided, which is the ibm cloud kubernetes service and managed service offering to create kubernetes clusters.

B

As you would expect, um it's a certified kubernetes offering through the cncf certification program, and if you want more information about this service and using it, you can check out that link there, but basically it's a kubernetes service and in that we implement our ibm cloud provider to provide the cloud functionalities for the kube clusters that you create.

B

So next slide. Please! um So then our ibm cloud, kubernetes service has provided two releases this year um in 2020, uh 117 and 118. kubernetes, on the other hand, um has provided the 118 release this year and working on 119., normally there's four releases a year and there's been a couple things going on. That has impacted 2020.

B

Of course, the global pandemic has made a lot of changes to life, and then coop community has adjusted as well and there's been a lot of feedback from user communities and developers on and and other cloud providers on, the speed at which kubernetes moves as far as the releases are concerned, so normally with four releases a year, you end up out of support from cube community in in less than a year, if you're not staying up on the current releases, so it can be pretty daunting tasks for some to keep current with that pace.

B

So there's been a lot of discussions in this area about the need for maybe long-term support or adjusting the release life cycle and support cycles.

B

So this is well not directly impacting the cloud provider sig, but it certainly impacts all the cloud providers as far as the service they provide building building on top of kubernetes, whether it's a managed offering or a product. If you will so I've laid out on this page, uh our latest releases, as you can see um when they were provided and when they are unsupported and um the we released the the versions of kube, uh usually about 45 days after the community. So you can get an idea of when cube released their versions.

B

So this is pretty quick um speed at which to keep up. So, um if you're interested in more about the topic on cube releases and patching and release life cycle and potential changes, there, please reach out to folks on the working group, lts channel and there's some links on that channel as well. If you're interested for the cloud provider there's um interest in extracting all of the code from kubernetes code base, that has lived there for quite a long time to move all of the cloud provider code out of the tree ibm, we were.

B

We never had our cloud provider in tree. So by the time we got to the show they were not adding cloud providers in trees. So there's no need for us to move. So it's more about our plans on open sourcing. What we have today, which we run as part of the kubernetes service here, all right next slide, if you will so, we also have the red hat open shift on ibm cloud managed offering so openshift if you're not familiar, is built on top of kubernetes and provides these additional features and functions.

B

You get with red, hat's, open shift management or their container application service. So we provide that as a managed service on our on ibm cloud, and you can see the versions that we have listed um on the slide as well, uh 311 and 43, and in fact today we just released four four so that I haven't. I haven't updated the documentation yet but um anyway, so those are available. uh Openshift43 is certified through the same certification program um that we have for our kubernetes service and it's based based on kubernetes version 1.16..

B

So if you look at openshift documentation from red hat you'll see that they move at quite a pace fast pace as well, just like the cube community as far as releases are concerned. So if you're interested more than one like, would like to learn more about openshift, please check out that link there all right. So now, let's get into what is the cloud provider? What does it provide for kubernetes? So you, you may hear us say the term ccm that stands for the cloud controller manager there was.

B

This is the current architecture on kubernetes for managing and working with the cloud.

B

This is done through the cloud controller manager, which has the main control loops, so the cloud provider say is responsible for owning those primary control loops and then the cloud providers themselves implement the interfaces that the control loops use in order to contact through the cloud connector the the cloud resources that it needs so um for ibm cloud provider.

B

We we run our cloud controller manager in the control plane um with alongside the kube controller manager, the api server and scheduler, and that cd and all that, and then we from there connect off to the cloud ibm cloud of course and make the uh application calls that we need to implement various features of kubernetes and that way it leaves the worker nodes um they they're.

B

They're kind of hands off from the cloud connections which they used to be hands-on, meaning they all would work directly with the cloud now, there's a little bit different approach here with this new architecture.

B

Next slide, please!

B

So then, um the if you roll back that even further and look under the covers at what the interface is and what a cloud provider provides. um There's a lot of different things, but these are the main ones and you don't have to implement all of them.

B

In fact, you can write your own cloud provider to run on top of any any cloud, really that you want and make it be whatever you want it to be, for the ibm cloud provider that we provide with our managed services and that we'd love to open sources.

B

It provides two main things number one: it provides load, balancer support for kubernetes, load, balancers and, depending on whether you're running on a classic infrastructure or vpc infrastructure, you get different types of load balancers. So for classic you have a network load balancer that runs within the cluster.

B

It's either ip tablespace or ipvs, based depending on your configuration and then on vpc infrastructure. You get a vpc layer, 7 load balancer. So when calls are made for kubernetes to create a service that call is then sent off to the cloud provider. The cloud provider goes and makes the calls to do whatever it needs to do to create that load. Balancer for you in your cluster.

B

So that's uh that's one of the primary roles. The other important role for the cloud provider is to um provide data about instances or nodes in the cluster. So we in the ibm cloud provider we actually rely. We work a little bit different than probably you'd find in a lot of other cloud providers, in the sense that we rely on the infrastructure layer to do some bootstrapping of the node, and we grab that data from the node labels to populate the instance, data that is needed for kubernetes.

B

So, for example, you may want to know cube, wants to know what region or what zone is a node in, so that it could properly attach labels. You know, what's the other information from the cloud provider that it needs, such as ip addresses and such so that that data is provided to the instances interface and now at 119, uh the community's implementing the instances v2 interface, to try to streamline the connections to the cloud so we'll be looking at implementing that in the cloud provider as well.

B

um The other interfaces the zones one is is is tied uh to instances and load balancers, um and it's very similar in that structure. We do not implement clusters or routes interfaces.

B

As far as routes are concerned, we rely and our managed services rely on calico to provide the implementation for the cni and do the routing within the cluster. So as a cloud provider, you're you're free to pick which interfaces you choose to implement or not, and what features you provide through that all right next slide, please so, then, just to wrap things up. What are we looking at towards the future uh on our cloud provider?

B

Well, we for sure work with community and kind of keep pace on what's going on on the sig cloud provider front. So to that end, you know we'd like to open source our cloud provider for folks that are interested in using the ibm cloud provider outside of our managed services right and then we to that end, we'd have to prove some documentations on how to set up your cloud provider, and then we continue working on aligning our build tests and release processes with the community.

B

So there's there's ongoing discussions with all the cloud providers about. What's the best way, you know for everybody to be consistent about how they should build their club controller managers. You know where should they submit tests and how should that be done? And you know what should versioning process look like so there's some consistency at class cloud providers, so those discussions ongoing and they impact you know all the cloud providers and we continue to you- know- make adjustments on ours to handle things like what was in.

B

You know, 119 to provide a new instances, v2 interface.

B

So with that uh overview of ibm cloud and our our sub project of sig ibm, our sig cloud provider would like to say thank you and I'll turn it back over to you.

A

All right, unmuting myself! Well, that was great, so richard. Thank you so much and uh thank you so much everyone uh for watching this video uh please reach out to us through slack channel or through mailing lists or emails.

A

As you know, as we mentioned earlier, we would love to have you to contribute to the project and making it better making cuban is better. So thank you so much with that. I'm gonna stop my stop shedding richard unless you have anything else to talk nope, nothing else. Thank you.