Kubernetes Kubernetes Contributor Summit - NA (San Diego) 2019, 27 Nov 2019

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Contributor Summit NA 2019: Intermediate Contributor Workshop - k/k walkthrough

Description

Event link: https://events19.linuxfoundation.org/events/kubernetes-contributor-summit-north-america-2019/
Session link: https://sched.co/Wrh1

A

Can everyone hear me, okay with this mic? awesome, sauce.

A

And so the main reason why I'm wanting everyone to get started on this now is.

A

Because, in order to make the internet reliable, they've had to slow it, down.

A

And,, but so just as long as everyone kind of gets,.

A

Gets a jump on this and if you haven't started cloning kubernetes the core repo.

A

Also start that now. you'll have plenty of time.. Are there questions?.

A

So the comment was that it looks like it might take some time to go, get kind.

A

So all right, sorry.

A

Yeah,, it's um,. We will have time because we are going to start working with this after lunch.

A

And right now we are only going to do the code walkthrough., so we should be,.

A

We sh, we should be okay., don't worry.

A

But that's why this slide is up right. Now.

A

Um,, if you need,, if you need a hand,, if you need some help,, I see your hand.

A

Yeah, sure. but sure. yes.

A

A

I think the question was over there. yeah.. If you.

A

Is this command working?.

A

Oh,, you mean a semi-colon after the on.

A

Okay. yeah, yeah, yeah, yeah, yeah, for sure. um,.

A

How's this? all right.

A

Yay. group debugging.

A

All right,, so this will be the last presentation before lunch. so,.

A

Um, I'm looking forward to this one.. Let me scroll back.

A

All right., who here has poked around the kubernetes code, base?.

A

Who here has opened an issue against kubernetes?.

A

Who here has open a pull request against kubernetes? all right.

A

Getting fewer. who here has successfully merged one of their pull requests against kubernetes?.

A

Well, done, sir., well done., um,,.

A

Who here has taken a look at the kubernetes core repository and gotten a little.

A

Scared? I have,.

A

Um, this, this particular introduction is a brief overview of where all the interesting.

A

Parts in the kubernetes core repository live. um,.

A

There are a couple of really common gotchas that not everyone is aware. Of.

A

And my hope is that with this, that after today, you will not stumble over this.

A

Um, when we say kubernetes, we often mean the kubernetes mano lists,.

A

Uh, could be in eddie's is a huge repository with many,.

A

Many areas. and as bob already mentioned, earlier,.

A

Lots and lots of our community groups own different parts of the code base and.

A

Somehow they, the code has to talk to itself and all the owners have to talk to each other and.

A

It can be really, really difficult to get your bearings. um,.

A

The other thing when we say kubernetes is, we are talking about, um,.

A

Kubernetes kubernetes on github. kubernetes is the org.

A

Kubernetes kubernetes or, as we often refer to as k8 kay, um,.

A

Because we're lazy and we can't be bothered, um,.

A

Is the core repository.? This is where most of the kubernetes code lives.

A

This is where all the binary's that you use as an end user, um,.

A

Get made. and,, um,.

A

Contrary to expectations,, this is also where a lot of the client code lives,.

A

Which is fun and interesting. um,.

A

But despite this,.

A

I'm going to be bouncing between the presentation and the code, um,.

A

For most of the rest of this hour. um,.

A

But keep in mind that there are still parts of kubernetes the ecosystem that do.

A

Not live in the core repository. most notably, um,.

A

Our test in fraud does not live in kubernetes core.

A

I do not know where the pointer went., I think maybe chris snagged it.

A

But on the bottom right you can see the kubernetes test, infra. um,.

A

That is where all the automation lives that makes the bots work.

A

It makes you pull requests, work and puts all the labels onto things and merges.

A

Your pull request when you're done. um,.

A

The kubernetes website is where we do all of our documentation or a lot of our.

A

Documentation, I should say. um, and you are already go getting kind from kubernetes sigs.

A

There are a total of 190 repositories in the entire ecosystem.

A

That's the bad news.. The good news is: there's lots of places to get involved.

A

Um, and without further ado,, I am going to go and head over to kubernetes and actually, let me go ahead and.

A

Make sure that I'm all set up for this.? I have notes.

A

So, who can see my screen and do I need to make it bigger?.

A

How's that? great. okay,, so here we are, and it doesn't look so bad, right?.

A

There's a few folders and then there's a bunch of change. Log mds that probably.

A

Mostly have words in them about the change log.

A

And then there's a make file a go: mod. actually,.

A

Kubernetes is using,, uh, uh, go modules,, um,.

A

As if the last few releases,.

A

Let's start on the top. somebody who's really excited about go modules., yay.

A

Um,, so the dot github folder is administrative.

A

This is where we have our issue: templates. um,,.

A

Unless you were involved with contributor experience,, you probably will not necessarily be super interested.

A

Um, in this part of the repo, um,.

A

Go depths. this,. These are literally licenses and owner's files.

A

Again, administrative.

A

A

The next folder is interesting.: let's go back to the presentation that makes sure we track api.

A

All right. um, the api folder is interesting because it looks like this is where the kubernetes.

A

Api lives.- that's not true.,.

A

I'm sorry.: this is not where you find the api primitives., this is,.

A

Um,, this entire folder is actually auto-generated.

A

And, um,, what happens,?

A

What happens here is the only thing that lives here are the rules under which.

A

The ap,, the kubernetes api apis get generated. um,.

A

You will also see this is not a super active folder. Last year,.

A

Three months ago, up, well,, there was a violation exception added three days: ago. um,.

A

But if you want to deal with api objects,, this is not the place to look.

A

So I've talked a lot about where things are,, I mean,.

A

Where things aren't in, not a whole lot about where things are. um,.

A

This will be a theme for this presentation.

A

In the build folder.

A

There are a lot of tools.

A

A

A

This kind of leads me back to.

A

A

Mmm., so it's a huge community repo. we have thousands of contributors all over the world.

A

everyone and their uncle have to decided that,.

A

Well, alright,, I don't want to misrepresent things. um,.

A

In this folder in the build folder and there's another folder,, much like it, there, live helper scripts, things for specific uses,.

A

Things that get used by automation and tooling, um,.

A

Things that you might use, if that is your situation and your setup. um,.

A

We welcome anyone who wants to come in here and clean up. um,.

A

We welcome anyone who can fix the documentation on this. um,.

A

Some of this is absolutely valid and absolutely useful and you will run into.

A

Some of these shell scripts. um, for example,, when you're running, uh,.

A

When you're running a cherry, pick script, uh, for a certain phases in the release when you're running test scripts,.

A

Some of them live in here.

A

I was going to show you one of these test scripts in my demonstration earlier.

A

Before the network failed, me. um,, so apologize about that.

A

Um,, the next folder.

A

A

this one too is a historic folder.

A

You will see things like juju,, I don't, I remember,.

A

I remember meeting one person who was provisioning clusters, this juju. um,.

A

So this is, uh,- this is basically, um,.

A

Where cluster provisioning code used to live.

A

A lot of that code is now provider specific and lives in kubernetes, sigs.

A

Um, and many of these things, are,.

A

You know,, some of them are being used by some folks, but they're very, very,.

A

They're, mostly here for historic, reasons.

A

Alright,, so let's go back and see where we're at.. We talked about build,.

A

We talked about cluster.

A

And now we are going to talk about the command folder.

A

This one is actually going to be interesting.

A

By the way,, do we have questions so far?? There's a question in the back.

A

We're going to give you a mic, so every everyone can hear your question.

B

I vaguely remember reading somewhere in some read me something about building with make versus baisal.. What's that all about?.

A

Um, so yes,, the answer is yes.

A

Um, you can do both. um,, so basil is the open source version of an internal google tool called blaze.

A

Um, and what uh, bazell does,.

A

I believe is: it builds your dependencies from the ground up for your system in.

A

Place. so where a make script can fail, because you don't have the correct dependencies,.

A

Uh, bazell at least attempts to just make all of those for you.

A

That is my very uninformed, um,.

A

You know, bird's eye view, understanding of the difference. um,.

A

Both are valid ways to go., thanks for the question. um,.

A

Now, where were we?, we were in the command folder. all right,.

A

So here are some things that should look familiar., kube,, adm, kubekuddle,.

A

Kubelets. um,: let's talk about,.

A

Let's look at the kube lit. um,: here's kuba dot, go.

A

This is where the kubernetes binaries live.

A

This is the main compiling code for the kubelets.

A

Mmm. capital of gotchas. again,, so there's kube proxy kube scheduler.

A

If you look at hyper, if you look at,.

A

Um,, what is it?.

A

So here's a kube api server.

A

Medium kube mark is,, I believe, um,.

A

It is a thing that used to be used for testing. yeah. hollow node.. This is, um,.

A

These are,, this is code that is meant to bring up cluster like object, so that you can run.

A

Tests against them without using a whole bunch of machines.

A

Uh, next we have another historic folder., docs.

A

As I already mentioned, the kubernete stocks.

A

Don't live here. there's a good ignore.

A

There's a build file that got modified two years ago and an owner's file.

A

We will talk about owners files, uh, later this afternoon.

A

But in the meantime,.

A

The way the, the place where you would find docs.

A

Is at kubernetes slash, website.

A

This is where the api ducks get billed.

A

And this is also for the reference documentation lives. I believe. um,.

A

The kubernetes documentation folks have their very own sig.

A

So if you're into writing docs and making things accessible for users,, um,.

A

This is the place to start.. I am also told that they have an excellent onboarding process as a sig.

A

So again, this folder is mostly historic.

A

I will say this word historic, a bunch of times.

A

Um, our next place is the hack directory.

A

I circled the build directory that I already talked about., some of the utility,.

A

Uh, scripts live in build,, others live in hack.. There is no rhyme or reason,.

A

But that's okay, because now you know that this is where things were.

A

So here are some,: here's the go, lind failure; script that I was going to show you all earlier when.

A

I did my demo. um, here. Is the cherry pick script that I talked about. this is,.

A

These are some scripts that you might use given certain situations. um,.

A

Test scripts. um,.

A

I encourage everyone to poke around in this,.

A

In this folder and see what they can find and see, what is useful.

A

We desperately need some bash wizards that can fix, um,.

A

Our many, many helper scripts. um,.

A

So far we have had,.

A

We have learned, here's where the commands are,.

A

Here's a whole bunch of historical things that are no longer really of interest.

A

And here's where the helper scripts live.

A

Next. [inaudible] the logo folder., it is tiny.

A

It's purpose is obvious., this is where the kubernetes logo is hosted, and that is all it does.

A

It is absolutely up to date, useful and relevant,.

A

But not necessarily, if you want to hack on things,.

A

A

Questions so far before I delve into the package folder.

A

All right,, so the first thing that you see in the kubernetes package folder are the top two.

A

Folders. they are called api and api. is.

A

Anyone have an idea why that is?.

A

I hear mumblings.

A

Historical reasons. very good. um,.

A

It turns out that the api folder is the original kubernetes api.

A

It's got pods,, it's got services and I believe persistent volumes. Look at that.

A

Um, and then people kind of saw, kubernetes take off and they're like, oh,.

A

It does all these things., wouldn't it be cool if it did all these other things as well?.

A

And so the api is folder was born, and this is where you find things like.

A

Admission, registration and authentication and um,.

A

Events and our back and all these other really cool things that kubernetes does.

A

For us., I see a question in the back.

A

So why didn't they just integrate it into the api folder? um,.

A

You know what,, that's a really good question. and I'm not entirely certain.

A

Um,, I believe it has something to do with the way that the objects are built and.

A

Depend on each other. um,.

A

So it's, this is,.

A

I'm sort of going to answer that,, but it might actually confuse you further.

A

Um,, so the next thing that I'm going to do,, so they actually kind of did this before we go on with a package folder, where a.

A

Lot of exciting code lives,, we have to take a shortcut to the staging folder.

A

Let me take a step back.. We have a huge mano repo.

A

We have so much code living in kubernetes core that it takes multiple community.

A

Groups to manage it, to review it.

A

We have owners files all over the repository and the folks in those owners files.

A

Only our code owners of that part of kubernetes. um,.

A

There are very few people who are top level owners.. They exist,.

A

They have super powers.. I am not one of them.

A

So, on the top level, kubernetes,.

A

We are going to go into this staging folder.

A

Um,, when I first heard that there was a staging folder,.

A

I was thinking in terms of ci,, I'm like, okay,, so I'm going to deploy to staging first.. This is not that.

A

This is completely not that.. What this is is.

A

It is an [inaudible]., the staging folder exists with the goal of breaking up the monolith.

A

That is its main purpose., so what is happening here is we are staging a lot of code for eventually living.

A

On its own, on their own repository.

A

If you look at the read me,, they are a whole lot of things of concepts. Binary's commands,,.

A

Um, that have plans to be broken out into out of the,.

A

Out of the monolith. um,.

A

So I'm going to go into the most common example, and that is kubernetes client.

A

A

Who here has used the go client for kubernetes?.

A

Who here has gotten confused? Because there is an actual client go repository and.

A

The kubernetes org. yeah., so this repository kubernetes slash client go currently is a lie.

A

You can't do anything with it. um,. Well, you can do some things with it,.

A

But what this is,? It is a mirror repository of code that lives in kubernetes core.

A

In the staging source. k8s io.

A

A

Let me split up my screen so that you can see them next to each other.

A

Maybe here we are.

A

A

On the left is kubernetes, kubernetes, staging source,.

A

K8S io clients, go. um, and on the right you have the regular go client for kubernetes.

A

There are a number of these mirror repositories.

A

Some of them will have a warning on the top level. Read ne that says,.

A

Please don't try to contribute here..

A

All code should go into kubernetes core.

A

Others I believe,, including the go client,, don't do that.

A

They just kind of,, so in the staging folder there isn't even a read me and on the client go it.

A

Says,, oh yeah,, this is,. This is the go client.

A

Yeah., so this is,. This is your warning, who has gotten tripped up by this by the way?.

A

A

current., the current source of truth, is kubernete. slash. staging.

A

Slash. source. slash. swords., it's this one on the left. um,.

A

Because if you notice actually, um,, they are still being mirrored pretty much.

A

Exactly., if you look at the k8, ci robot right, here,,.

A

It says: merge, pull request, number eight, five, three, oh five, and that is the exact.

A

Same pull request that is merged into client. go.

A

Even though, like client go doesn't even have that many pull requests against it.

A

C

So, at a dot, release. um,! Why wouldn't you just move it all over to the new location?, I'm sure there's,.

C

It's impossible,, but I don't know.

A

There are a lot of dependencies by,, there are a lot of interdependencies and they all have to be solved before this.

A

Happens. and to be entirely truthful with you,.

A

I cannot give you a good answer for this, because, most of the time when I talk to.

A

Maintainers, who are in charge of this migration, um, they,.

A

They don't want to talk about it.

A

So, um,, but I have seen,.

A

I will tell you that I have seen code move from the core repository to the.

A

Staging folder in preparation for breaking out.

A

So my hope is that things are happening and you can be part of it.

A

That is an excellent question and not one. I am prepared to answer because I.

A

Don't believe so. um,.

A

The other really cool thing, is,.

A

Is that in the kubernetes core repository,.

A

You will see imports that these mirror repositories,.

A

Which I don't even know how that works.

A

and go definitely says you shouldn't, do that., but it is definitely a thing that happens. so that's,.

A

That's also incredibly fun., so client go is just one example of these mirrored repositories.

A

Let's go back and I'll make this film again.

A

Um, so in summary, whoops, I haven't even talked about the api apis yet. um,.

A

Let me go back to that. um,, but in summary,.

A

A lot of stuff will live under kubernetes package and a lot of stuff will live.

A

Under kubernetes staging and we will be turned to this dating folder and talk a.

A

Little bit more about that. excuse, me., um,,.

A

So I gave clients go as an example, back to your question about the api apis.

A

Here, [inaudible] and kubernetes io in the staging repository.

A

Keep in mind when the staging right now,, the top level folder, says api,.

A

You got your wish., it all lives in one place., now,.

A

Um,, the former,.

A

The former core api.

A

Has its own place under core slash b, one.

A

If you poke around in here,, you will find,.

A

You will find under a register,, I believe it's in register,.

A

You will find that here.

A

You can totally look at these things., add known types,.

A

Node even lists secret pod.

A

So here are some pod,. Let me find it. c pod.

A

Pod. exactly. so add known types..

A

This is where we're adding all of the kubernetes raw types.

A

Um, and [inaudible]., it is all part of one api in dislocation.

A

To summarize, because this is another of the gotchas.

A

It's like which api am I dealing with, and where does the api live?.

A

In a package folder, you have slash api and you will find those types in the.

A

Staging folder under api core v one and what was formerly api apis is now just.

A

Api, which incorporates um, the old types.

A

Anyone's still confused. all right,.

A

Let me try and say it in a different way.

A

Nope,, I don't want to go there.

A

Over here in the kubernetes kubernetes packaged folder, we have code that refers.

A

To pods services, the original api and we have an api apis folder that contains everything else.

A

Nowadays, we think of all of those as one api because of the migration efforts.

A

Under kubernete, staging source,, we now have all of this combined in one top level. Api folder.

A

If you are looking for the types that over here in package are in the old api.

A

Folder,, they live right here.

A

And you can't see it from the file names., but if you actually look at the register,, if you actually look at the types that are contained, inside, like right, here,.

A

If you look at types dot go or register dot go, you will find the original communities api, types., um,.

A

Yeah, this,: this might also be something that you have to look up by yourself. A couple of.

A

Times or discuss it or talk it back at someone,, um,.

A

Which we're all friends here,, so I encourage everyone to do. That.

A

A

So if you look at the file structure next to each other,.

A

You will see that the package api apis looks very,.

A

Very similar to the api folder.

A

But if you're confused,, because if the naming,, this is why.

A

We've done that, we covered that..

A

Let's look into a couple of more other things. yeah.

B

Wait,, what is actually [inaudible]?.

A

So when we build kubernetes, um,, we actually,.

A

Um,, so these apis are actually just definitions and registration of api types.

A

So you don't build those., it is literally like this is api machinery kind of stuff. um,.

A

I will get back to the rest of your question.

A

I hope, as we go on, I'm sorry.

A

The question was: where do we build the kubernetes binaries? um,.

A

And we are actually going to do that in a later demo. so,.

A

So let's look at a couple more of the folders in package because there's some.

A

Interesting stuff in here.

A

So here's, here's some, um,.

A

Some of these,, some of these folders are going to be extremely descriptive and other ones are.

A

Descriptive and you think they are one thing and they're really, really not. um,.

A

But off is what you think it does. um,.

A

It talks about authorized his authorization inside a kubernetes cluster.

A

A

Capabilities has something to do with,.

A

I can't actually remember at this point. um,, oh yeah.,.

A

Manages system level capabilities., it says right: here., um,,.

A

I feel terrible for reading something out that you could've read: yourself. um,.

A

Client, uh, used to contain client code no longer does.

A

We already talked about clients, go.

A

Cloud provider is another one of those historic leftovers.

A

Um, we have many different cloud: providers. um, they have their own sig. um,.

A

Each cloud provider actually has their own, uh,.

A

Forked repository in kubernetes six that you can go check, out.

A

Um,, so this is what it's telling you.

A

it's deprecated and a lot of these cloud providers live somewhere, else.

A

They have enhancements. um,. This doc hasn't been updated in quite awhile.

A

Um, controller controller is cool.. This is what runs all the objects.

A

So here you will see just by the description of what's going on. Here is the cron.

A

Job. we can take a look in there.

A

He was the cron job controller. there's some documentation. um,.

A

And this is basically where the objects where the objects get made.

A

Volume service. um,- all of this looks, should look pretty. um,.

A

What's the word?, I'm missing? a word. familiar. thank you. um,.

A

This should look pretty familiar to folks. so, um,. This is the controller code.

A

Let's go back to package, um,.

A

Credential provider.

A

This one is basically what it says on the box. um,.

A

But this is,, this is, uh,, this is,.

A

This is a little bit of extra code that you might need.

A

So you can use kubernetes from private repositories if your code does not have.

A

Access to public good hub.

A

here are some things that people have worked on to make it work on their own.

A

Private github, or whatever they use. um,,.

A

I wouldn't know because it's a private, um,.

A

Feature., this is for feature gating., um,.

A

Feature gating is important when we are trying out new features that are in.

A

Alpha. feature gating is important when we're not sure if something's going to break.

A

Things. um,: this is where that happens.

A

Um,, I actually have zero idea. What field path does.

A

And there's a dock and,.

A

All right., it's supplies, methods for extracting fields., alright, cool.

A

Um,, so I'm going to go ahead: and, uh, just, just talk about a few more of these.

A

A

Kube api server.

A

Is where all the things live, that the api server needs to run? Admission,.

A

Authentication, authorization,.

A

Mmm. kube control, kube lit., these are, um,, you know,.

A

We all know what these are and um,.

A

This is some of the command code. um,.

A

What's the difference?, this is where all the logic lives.

A

the command directory literally, has the main dot go file for each of these.

A

A

pretty much. um,.

A

A

Oh,, I thought you were coming up and grabbing a microphone and correcting me..

A

This is entirely possible.. I am not,. I am not by any means.

A

Those super authority on all things: kubernetes, core., um,,.

A

If you all want to learn, more, um, go get involved with sigs,. Go dig into the code,, go work on it.

A

No one knows all the things with blake.

A

Maybe a handful of exceptions.

A

Actually. I'm willing to bet.. No one knows all the things, because there are so many separate niches and like.

A

Provider specific areas of this code that it's,.

A

It's gotten quite out of hand. um,, let's see.. Now where was I?, let's see.

A

Mmm,, I have been talking about, um,.

A

The folders in the kubernetes package, directory. uh,,.

A

Cloud provider controller.

A

I even had a slide for you. um,.

A

Credential provider features kube api server, kube control, kubelets.

A

Um, kube mark iben again mentioned this- was an attempt, um,.

A

That I'm not sure what the state is, um,.

A

To have a fake kubernetes cluster for the purposes of,.

A

Um, metrics generating metrics and compare it and uh, and getting information.

A

A

The master directory is leftover for historic, reasons.

A

The api,, the community's control plane used to be referred to as the master plane, and it.

A

Is now the kubernetes control, plane. um,.

A

I'm not sure why it's still sticking around, probably because of some redirects.

A

And dependencies. um,.

A

But let me assure you that, where you want to be is kube api, server,.

A

Not the master, folder. again, just be aware,.

A

We are still in the package directory and I keep doing this and it's not what I.

A

A

So, who here has used kube control?, kube cuddle?.

A

Mmm., the printers folder is actually where a lot of the code lives.

A

That makes you a kube control output, look pretty.

A

So this is,, this is what makes everything look like a nice table and not a jumble of logs.

A

We all love logs., that's great.,.

A

A

Let's good back here.

A

Um, proxy has code related to kube proxy.

A

I am personally not super familiar with kube proxy on,. You know,.

A

A personal, I'm not really on a first name basis with it,, but if this is you,.

A

This, where you would find that.

A

A

This one contains logic for things like resource and memory, quota.

A

Um,, it's not a super enormous uh,, folder,, but, um,.

A

We do want to make sure we have it, because it's important for things like.

A

A

I have no idea.

A

Um,, I really don't know. um,.

A

Somebody decided it was a good idea to put it here at some point.

A

Who here is on an operations team for like,? You know,.

A

A large system that's, you know, more than three years old.

A

Um,, so what do you see here? yeah,? Why doesn't this live? Here?, well,.

A

It would be great if it did,, but it currently doesn't, because it organically grew from a thing.

A

One thing led to another, and now it's here and here we are. um,.

A

And yeah, there are, there are always efforts to clean up the code. There,.

A

A whole code cleanup label., and I really encourage everyone who sees something that they don't like.

A

This is,, this is actually a great opportunity, right?, so many skeletons,.

A

So many things that don't make sense. um,.

A

Go ahead and go ahead and get involved., let's see.

A

Um, we have 15 minutes until lunch,, so that is,.

A

That is all the time we're going to spend on this, um,.

A

Registry., this is storage related.

A

Scheduler. um,.

A

This is where logic for scheduling pods, lives.

A

Let's take a quick peak.

A

Um,, this is fairly busy, fairly involved.

A

There was a whole sig called six scheduling that is involved with this part of.

A

The code base., if this is you get involved,.

A

Um, security, similar thing,, what it says on the box. um,.

A

What kind of security resources do we have and security context is about what.

A

Security resources. We are using.. Let me get back to my present moment.

A

Um, service account has logic, whoops for accounts.

A

A

As this age is not actually,, what do you think it is?.

A

Again,, if we're going to peak in here,.

A

Ssh has something to do with metrics.

A

It's not really authorization related., um,.

A

I'm unsure why it's called ssh. um,, so these are just a couple of the things that you might find that aren't,.

A

That don't make a whole lot of sense.. Um, utill is another helper script. Folder.

A

Volume is related to storage. again for system volumes. um,.

A

Windows. this is where,.

A

This is some of the places where attempts at making kubernetes work with windows.

A

Containers., who here works on windows?.

A

Oh, my gosh., you are brave people.

A

I, no, no,: this is great. I,. I love it.

A

I love it. um,, there's uh,.

A

There's a whole sig windows for you just for you that involves kubernetes.

A

Windows and everything related. um,.

A

I very much hope that they will be at the sig meet and greet because that will.

A

Be the sig for you. alright,.

A

So this is, this was the biggest directory in the kubernetes repository outside of the.

A

Staging directory. um,, we are back at top level.

A

Plugin. um, what, no,.

A

That's not what I want.. The other button was yellow.

A

Um,, it used to be that some of the things, um, in kubernetes were plugins. um,.

A

This is actually a little bit of surprising, um,.

A

Admission and off used to be plugins and not their own thing. um,.

A

They're their own thing now,, but some of the stuff lives still in the plugin folder.

A

A

So if we go and look at the plugin folder,.

A

You will find a thing: that's actually.

A

Here we are. some of these things should look familiar.

A

Always pull images., you know, like when your,.

A

When your image goes stale and for some reason, your thing won't ship, because it.

A

Can't find the docker image, because the pod is not pulling the image with the.

A

Changes. it's,, you know,, it's still broken and you're like,. Why is it broken?.

A

I'm shipping the thing. and then you sent always pull images to true.

A

This is where that code lives.

A

So this is another interesting one.

A

It's still in a plugins,.

A

So known restriction four days, ago, 10 days, ago.

A

I always like looking at what happened, um, about the most recent changes.

A

Right? I like to look at the dates.. If something says three years ago was the last change on this,. I'm like, yeah,.

A

Okay., I'm not even sure either. it's working really,.

A

Really well, and it doesn't need changes or it's not being used right. Now.

A

So back to the staging folder.

A

We already talked about the api and I can give you brief. Overviews.

A

So recap, a lot of the stuff that used to live in package now lives in staging,.

A

But it's not top level..

A

I'm in the publishing folder is all the logic where we keep all the mere repost.

A

Instinct. um,, so that's a lot of automation, instrumentation. um,.

A

You go to source and then you go to k8's. Io.

A

is anyone unfamiliar with k8's? nope, we're good.

A

Okay. short for kubernetes, pronounced k8's, pronounced kubernetes.

A

Both are correct., we talked about the api, folder. um,.

A

Api extensions, api, server,, um,.

A

Is the place where logic for crds lives.

A

This is where you would go to find custom resource definitions.

A

Um, [inaudible].

A

Let's go ahead., I don't want to tell you the wrong thing..

A

So let me just reference my notes.

A

Here. we are. cool.

A

So in api machinery and api server,.

A

These two folders are actually related. um,.

A

This is where the logic lives that makes the api work.

A

So here's a whole nother package, folder.

A

Mmm. more api, apis.

A

Mmm. but,, but this is where the actual logic lives and not the registration and the.

A

A

Let's go back. um,, so api servers related to that, um,.

A

Cla one time, um,: this actually has a generic helpers for kubernetes related cli tools.

A

Um,, they actually have a read me. I believe.

A

yeah. kube cuddle, commands, kube, kuddled plugins.. If any one of you has ever used, customized, customized, started out as a kube control. Plugin actually started out as its own sub.

A

Command, but then now it's part of kube control.

A

Um, we already talked about clients, go, uh, cloud provider,,.

A

I believe this is another one of the historic repos.

A

So is cluster bootstrap.? Those are like,.

A

We wanted to have cloud providers specific code..

A

We want to have cluster provisioning, code. um, code, generator,.

A

Um, is a place where a lot of the logic lives that uh,.

A

Does that generates, um,.

A

That autogenerates the api definitions inside the repository.

A

We can talk a little bit more about that in detail in person. um,.

A

But I want to continue with the overall overview. um,.

A

Component base was an attempt to clean up and refactor.

A

And it's an ongoing attempt.

A

So it's basically,.

A

I'm trying to make sure that we don't have so many definitions of so many.

A

Different things and all the same place. um, this might be a good place to get involved. If you are very familiar with.

A

Kubernetes objects, um, and wanting to help do some cleanup.

A

Mmm., let's see.: where are we at??

A

We talked about these talk about code generator component base,.

A

Uh, cri api., this one, um,.

A

Has to do with container runtime.

A

Uh, csi translation lib is container storage, interface, related.

A

Um, storage is one of the things that I am very much not familiar with, because, where.

A

I work, we don't keep,, we don't store things on our clusters.

A

We don't keep state. um,, but a lot of people do and a lot of people do really cool work on it.

A

and if this is you, um, here is some of that code.

A

You aggregator. this one is, um,.

A

This one is actually a helper for you when you have custom resource definitions.

A

And also the regular kubernetes api., this is the code that lets your api server. Pretend that it's all one and the.

A

Same thing, so that you don't have to have separate parallel processes going on.

A

For both. this one's pretty cool. um,.

A

B

Has all these components in one place.

A

Yeah, so there are kubernetes diagrams, um,.

A

And I may be able to find you something.

A

The problem with it is, it goes out of date, pretty fast.

A

So, um, so yeah., um,, and, and yes,. There are,.

A

There are diagrams, but they are really hard to keep up to date.

A

Um, but that's a really good question and I don't have one for you: today,.

A

But get in touch with me and I might be able to find something for you.

A

Right., where were we? okay., so oopsies? That was not at all what I meant to do. um,.

A

The next few folders have to do with a kube proxy,.

A

Kube scheduler, kube control, things that you're all really fairly familiar with it. and, um,.

A

When I first gave this presentation, the kube control code, all lived under the package folder.

A

and now most of it is in the staging directory. um,.

A

We have some legacy cloud providers.

A

One thing I want to mention about this folder: that is really the most important.

A

Thing are the last three of these sample api server sample cli, plugin and sample.

A

Controller., what these are, are well maintained, example, repositories that make it possible for you.

A

Um, uh,, these are tutorials., basically they're, very technical tutorials and they are unfortunately buried.

A

Really far down in this directory,, but they are some of the most useful places that you can get started. Hacking and.

A

A

They are frequently updated and they will show you if you want to build an.

A

Extension, api server.. If you want to build custom resource definitions,, um,,.

A

It's well documented,, well, maintained,, um,,.

A

And you should be able to use all three of these right out of the box and you.

A

Will learn a lot about how this works by trying it out,.

A

Um, and playing with it., so that is my recommendation to you.

A

We are almost done, and that is good because we are almost at lunch,.

A

Back to the top., so we talked about the most exciting places in the entire repository.

A

Most of the meat and potatoes is done.

A

There's a couple more folders. um,.

A

There is the test folder, which is,.

A

Which has a lot of the uh, integration tests in it.

A

Most of our test infrastructure lives in kubernetes, slash test in front,.

A

So you'd go here.

A

So when you open your first pull request,.

A

A bot will talk to you.

A

And who here has heard of prow?

A

source project because we notice it's not? Actually the only one that uses proud. proud is how we manage our pelvic quest. Workflow.

A

prow is how we put labels and sigs and assign reviewers in an org where we don't.

A

Get to click buttons and assign humans with like a mouse, click. um,.

A

I will,, I will give you a little overview of where these commands live at the end of.

A

Today, this afternoon. um,, but this is where the prowl code lives plan was also responsible for merging.

A

Your pull request. um,. If you gathered all your pull request, labels and everything, looks good and you.

A

Got all the reviews- and you have all the green flags and all the tests pass and.

A

You pull the closest just kind of sitting there and there's no button that says merge. now. The reason is because prout is waiting, and in this case it's actually a sub.

A

Command of prowl called tide.

A

Tide is waiting in emerge pool and you pull request is queued to get merged.

A

Someone's laughing. yes,- these are all team, themes., um,.

A

I'm not sorry..

A

The idea is that the tide takes your pull request and washes it into kubernetes.

A

A

We are back on kubernetes top level.

A

A

And then third party code is mostly kind of like vendor,.

A

But in a different place for legal reasons and licensing reasons.

A

Um,, most of the time, you're not going to have to worry about this. um,.

A

Translations., this is actually about human translations into other languages.

A

So if you want to translate docs, um,, if you want to add things,.

A

Here's,: here's some examples. um,. If this is you,.

A

If you're, tired of all the english centric nis in computer, programming,,.

A

Um, vendor, uh,.

A

Some versions of kubernetes still use go before go. Modules were a thing.

A

This is that this is literally a go vendor code. um,.

A

We have a couple of good files and then we have a ton of change. Log files,.

A

A license, a make file, a top of our owners, file.

A

I actually wonder who's in there.. Some of these people should look familiar.

A

Tim hawkin, brendan burns.

A

All right. do we have any questions before we head out to lunch?, because this is the last.

A

Of the core repository and you know,, it is lunch time.

A

Questions. yes,.

A

There is a staging and not staging. okay. um,.

D

So, at the end of the day, you would do your work under staging and when you would.

D

Reference your work, from, um,,.

D

Below staging,, I mean above staging, right?.

A

So all the mirror repositories that happens automatically if you,.

A

You will do changes in the staging repository as of this day. yes.

D

Okay., I'm not sure that that was your question. Though.

D

Yeah,, I think it does.. I mean, yeah.

A

Do it in staging or in package. it depends.

E

A

Yes., it absolutely depends on where the current code is,.

A

And sometimes it's literally in two places because it's being moved over.

A

Yeah. all right., let's go eat.