Kubernetes SIG Cluster Lifecycle, 12 Jun 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kubernetes SIG Cluster Lifecycle 20180612

Description

Meeting Notes: https://docs.google.com/document/d/1deJYPIF4LmhGjDVaqrswErIrV7mtwJgovtLnPCDxP7U/edit#heading=h.k6sq8orkf4wg

Highlights:
- etcd issues
- Documentation for 1.11
- Kubeadm upgrade tests
- Cluster API alpha exit criteria
- Cloud provider documentation
- Themes for 1.11 release notes

A

Hello and welcome to the June 12 2018 edition of the cluster lifecycle, especially special interest group meeting on the humanities community. Let's see, let's pull up today's agenda bra. Were you here to talk about cluster API, alpha status.

A

Crickets, if not we'll push that down the agenda and come back to it, I'll see if he's around Tim, do you want to take the next one so.

B

This is just a PSA, because we've kind of we're kind of in the end of the cycle for 111 and we're a little bit in debug firefighting mode, not because a lot of people are trying to debug and validate and verify they just basically do testing, but just a PSA or reminder that slack is essentially ephemeral and writing up.

B

Good issues is probably a better way to communicate ideas to make sure that we have valid reproducers and to document those issues, because sometimes we might think we have a fix- and we may not right and having that logged over time is important, so I think just ensure a good process going forwards, because it helps everybody and I know it's hard, because we're trying to everybody's trying to do their level best, which is reasonable.

B

But let's just try and focus on the issues and log them and then rally on those if we can going for it. So that's first PSA I'll punt off to Jason and Lucas about the next thing.

C

Yeah so yesterday, when, when I was doing just this kind of firefighting, bug fixing I noticed a lot of or a couple of HCD problems and warnings in logs, so NASA. Fourth, so jason myself and chuck have been working on those and some others as well. So do you want to summarize jason the the fix that you came up with in the end here after after we had done some slacking yeah.

D

So there were a few different issues that we uncovered the first one was that we were not actually properly securing the peer port for @cd we're configured the client off, but because- and we assign certificates to it, but because we didn't set the the actual, listen URLs for the peers to HTTP. It basically was published discarding the TLS configuration that we had in place, so it basically was essentially an unsecured peer port, so the first PR linked in the notes.

D

Six, four, nine eight a addresses that issue, and it also increases the timeout for EDD, because there was also another issue where, during the upgrade between the manifest picking up the new manifest and also the EDD three one, two three two datastore upgrade it was taking longer than the default one minute that we're having for the upgrade so I increased the timeout to five minutes, which is sufficiently long enough that there should be nobody that hits that timeout I do want to follow it up with providing a note like Bluebird mayor suggested, but that hasn't been done.

D

Yet. The other fix in that first PR was also for updating the SANS that we assigned for the peer port as well, because it wasn't including localhost by default, so just to be able to bootstrap the cluster for a single node without any overrides. We don't really want to expose that port out beyond localhost, so just use localhost for that.

C

Yeah, but that makes it still easy easy to I could do a jail later on using the default. This is default. Yes, as Jason said, like three issues, I hope we have at least two of them fixed now using HTTP, so the default was HTTP and I.

C

I I would hope at CD in the future would be as smart as if you set the pair flags, it would default HTTP instead of just like you have to say both in order for it to be valid, but that is like not the state now, so we have to set both, which is done, that master, the PR just merged and increasing the timeout will also hopefully fix our upgrade tests that are currently failing. Rubin had some other ideas that we might want to look into with regards to the upgrade test.

C

Failing also I also sent a PR yesterday with a misconfigured testing. For the only thing we have left the the third HCD issue was about the clients, and several do you want to speak to that as well? Jason yeah.

D

I can so after we updated that cd32, we were noticing a warning in the TLS in the sed logs talking about TLS handshake issue after debugging for a while, it didn't actually appear to affect any usability within kubernetes, kuma DM and it was able to come up and everything was functioning after digging in for a while, I figured out that it's the G RPC gateway that was introduced by default in Etsy d-32.

D

It's attempting to use the server certificate as a client certificate to connect back so I have a PR out there, six five zero to zero and that one addresses updating the generation of the server certificate, so that it is, has both server and client usages similar to the pier certificate, and that resolves the the G RPC issue.

D

Now. One thing to note about that is that during upgrade, we don't currently remain certificates, so we may want to figure out either document and the troubleshooting guide. You know how to resolve that issue or some or introduce a way to automatically regenerate the certificates.

D

But that's that's a much larger discussion than I wanted to introduce a just, a quick fix, PR.

A

Yeah I love bug upstream against sed. It sounds like they are sort of misusing that cert or its at least. Miss named I know that internally Google when I talked to our security folks about certificates. They've said that it's it's better, not to use the same search for server and client, and it sounds like that's what @cd is doing here. Yeah.

D

There's an existing issue out there I, don't know the awareness of it, but I'll go ahead and I'll dig that up and I'll add that to the meeting notes as well. I also don't like the idea, like the peer certificates, drive me crazy as well. There should be dedicated search for each usage, I think yeah.

A

It would nice to have those issues sort of bubbled up upstream to that CD folks. So it's least on their radar and it's something we care about.

C

Yeah I also think we can open an issue for better order detection, if you specify peer sets, the default pair arguments should be HTTPS by default, instead of just with a silent warning or like kind of silent. Just warning in the logs saying that oh, we won't use your peer sets because you didn't say both I think that it's a fair enough thing to implement for future releases, at least so.

B

To step back, then, should we be making that change, or should we make the change now put a slash, slash to do in the cert that we're creating now, with 111 and cross-reference, the the issue that we file against St the.

D

Latter idea, because if we don't, we will not have a functional G, RPC gateway for the sed that we deploy that really shouldn't affect kubernetes. But it could affect the way that people are interacting and monitoring with the sed deployment.

A

Yeah that sounds right to me. I think that this is the right way to fix it in the short term, but we should work with the NCD folks, as jason said not just for this certificate, but maybe for all certificates to figure out if there's a way to split the peer search into actual client and server certs to separate those roles, better yeah.

C

Right I mean we can't really if this is the way to do it, we have to like, if we're deploying this version of it city, we have to go like play by the rules, but then talk to them about making it better in the future. It.

D

Actually surprised that.

C

D

Were no config options exposed for configuring, the gr, PC gateway it just automatically uses that certificate, there's really no toggles at all for it. So yeah.

C

C

Another so yeah I think I think that's that's it regarding the at CD CD stuff, really really satisfied with with the speed of this thrashing, like generally I mean 24 hours ago, we hadn't and I started with this, and now we already have like two three PS fixing stuff. So just a huge huge thanks, everyone involved, then we have other outstanding bug, fixes that's a metal rattling, the PR there yeah.

B

So I just want to I, know everybody's like debugging right now and there's a lot of noise and slack about all the issues that are going on. So I wanted to see if other folks had, if they're aware of any other bug fixes, besides the or bugs besides the sd1 and the blanket PR that Lucas put up for a bunch of minor bug, fixes.

C

So what I didn't have time to include there was.

C

This one or two small things with regards to dry run so I. So what I really want to do in you know Doc's, is to highlight the dry run mode more cuz.

C

A lot of people are like afraid of what is q, better minutes or upgrade gonna do and dry run like spits out everything cubed I would do, and you can also use that for your reference, like your bill, your own cluster, all doing the faces or whatever you can just do dry run and see what are the manifest that would be generated, but I, don't think were doing that good job in our Docs or not actually highlighting that so really or making that more visible is something I want to do for for 111 if, if at all possible, all right after and there's one I think one or two small fixes to make program work, there's some something in a DNS DNS stuff.

C

Could you login.

B

Issues so we have posterity free.

C

Yeah I'm gonna do that other than that.

C

So, with regards stop creating the the cubelets config locally on the node, the current implementation, just like, writes the file down. Do you think we want to checkpoint the earlier earlier file.

B

We already have a release note against this. If people are modifying the existing unit file, that's there. That's kind of you shouldn't be doing that anyways there's ways to expand it. So I I'm, okay, with with the release note with the current update, because you're you're not gonna, be able to affect it unless you put in a pre rule on upgrade inside of your respect, file and your debian, so you can.

C

B

Part of your packaging updates so.

C

I wasn't thinking about that. I was thinking about the cube, the version cubed configuration so after you've upgraded your cluster to let's say want well, you wanna, get that that little cube, less configuration for 112 is in a config map and you won't download that every node and when you run that command the down. Listen the thing it's just gonna override the 111 config, that is, there, do wanna, like somehow I think it's.

B

C

B

If the config map is stored, inside of the still I would think as long as.

C

We're the version.

E

B

Map from 111 and the 112 version, config meant I'm totally fine with just leaving it on the API server, because you always have posterity there. Yeah.

C

Yeah yeah true, if the 112 thing is bad, you can just run the same command against 111 yeah.

B

Your I have that command to pull down the config from the abyss. Yeah yeah.

C

Then then that's yeah, that's one l1 other with regards our basil Debs. That I got a ping on yesterday, so not not kubaton, but but I dab, something with C and I. It.

B

Was the directory creation yeah.

C

B

I commented on that individual issue and I was like I was surprised because I'm, not a debian expert for dipping packaging, but I, do have lots of history with rpm packaging and usually respects and can maintain and control your directory structures and blast them out at will. So, typically that should be defined inside the packaging role and that shelled out as a separate script to be to create it. So I think he closed the issue and he talked with XD about doing some other thing, I think the reason he closed.

B

The issue was because the fixed ease comment, not mine, yeah.

C

Ok, so there's some basil stuff, yeah Jeff just said you should use some other basil tools rule or something yeah okay. Well, we should really check that because, as Ruben pointed out just like, when I will go or something there's some kind of weirdness when installing the community and I dab in our EDD tests upgrade list. If.

B

We, if we can log issues for other stuff that we have for I, mean even yeah who's Robbie. Are you taking notes if you can assign action items for people to file issues on these things, I think that would be. Hopefully you can. You can poke me in our regular gets.

C

So yeah, that's the the most of the bug, fixes I, think for sure. There's there's some others as well.

C

C

Should be should be the most most of the stuff we know about right now,.

B

Right I think the next step on the list is basically about Docs.

A

Sorry Tim are you asking who has a status on Docs or you're, just asking and generally.

B

F

E

Speak about that we are okay in terms of the futures and I and the new commands we have. So that's not okay for the code freeze, we don't have anything else like it. The remaining surface, like refactoring of some of the pages, that's over what and so many ways and uh I mean I was speaking with Jennifer about this. We we should possibly like extend this like in the following weeks. We I don't think we can fix everything for today, because today is a dog freeze.

B

E

G

B

The config or Lucas you have the updated, config documentation.

C

I have something like staged locally about, like a draft of this is how you do the the nuke. This is how the new cubelets cubed M integration works, and here is like the new schema, but I have to consolidate that. What's what's a master in our Docs one general or one thing I noticed was oh.

C

Well, I'll just take a look at the latest.

C

Things merge so quickly, so just gonna revisit what's ATS head in the doc Creepo and try to put things up there, there are net new job net new Doc's in terms of what we already have and like updating our current alabamy said: I think we are in a pretty good shape, at least better shape than we've been some some earlier races, so Eric's very good I have.

E

More question about the the cupola configuration changes. Do you know like where should we put it in terms of the websites? I, don't bother location for it's.

B

Not the main installation guide you can let you can link out from the main installation guide and fine with that, but not the main installation good. No.

C

No yeah, so if we could move the or it should be somewhere under a cubed, a reference folder, but the exacta. You are a land on top but better duck under cubed in reference, and we should link basically.

E

Should be a separate page, you have to link pins.

C

Yeah separate separate taken, then we link.

C

E

Well, you can submit I, guess the Google Docs links for me, because I know you are using Google Docs for editing. You can share the link or maybe Jennifer can join too in terms of like copy editing before we submit the PR or if you prefer, we can send this as a PR and.

C

It's it's a bit rocky connection, but try I, guess it's I.

C

Think I think he got disconnected.

C

Yeah I'll think with you a little bit me run Jennifer if I, if I need comparing Thanks.

E

So in terms of the rather user stories you make, you create an issue for basically you create a list of user stories. What else do we have to add for one eleven? That is crucial.

C

Let me pull it up.

C

We have running easier tests against Cubert in clusters, but it's done I'm doing the package in Cuba diem and like doing cubelets I think we can punt the securing your Cuban and cluster further that that is already there, but it's in the general like monoliths cubed and reference guide, so splitting that up another dog can come during the next cycle. That is not critical.

E

So the one is writing about the quadrivalent arguments for Cuba diem and I mean II. Well, it's only like three sections in there I'm not sure what else to add to it and because so.

B

The this this dovetails with what I talked with Jason about and Liz.

B

This is out, but she had more experience on this space, but we changed the config so much that we definitely need a troubleshooting guide to help people walk through how you change the there were macro arguments that used to be in the config that now need to go into extra arms, so I think walking through the translation of what the previous config knobs did and how to pass them in is going to be pretty important because I guarantee you that the people who relied on some of those things you're gonna, start to file issues.

B

C

I'm, just in out we have automatic conversions and we have the cubed em config migrate command that can translate it for you client side, but but yeah it. Definitely that is some the thing I'm trying to write, but it's it's taking time and I got interrupted by someone say xeb stuff yesterday, yeah so.

E

What question here is: should we like explain the current config in terms of the XOR arguments for the.

G

E

And say that this is going to change automatically if you do a lot of greatness I.

B

Don't see how all the artists are going to translate to you to use. Did you do it upgrade conversion for all the artists that existed, Lukas, I didn't take all worked so.

C

How do me yeah so for all the config changes that I've done? There are upgrades they convert automatically, but I've only done like compatible ones. So far, I started with the easiest ones.

C

Yeah, okay! Well, we can take that via via github I guess, the.

E

Question is: should we have this as soon as possible or are their priorities in terms of the user stories.

C

I think that configuring, your control plane is, is a really important one. Yes, so so, if you, if you can write up like this, is how you like common scenarios like this, is how you do the API. So logs is how you do this, and this and this using the like concrete examples of the config file and saying that, for example, API server X drugs is gonna change, because, eventually someday we're gonna have component config, which is structured. This is just a string string, flag map, yeah.

B

What I can work with you little mirror on that and Jason I could take this off your backlog when we do that.

E

Yeah, basically, my problem is that I really don't have user stories like scenarios. I can explain what we have in.

G

Terms of the configuration folks, but they don't have stories. Let me let me write it down concretely I think yeah.

B

It's in my lists, we.

G

Have your separate.

B

Issues and I'll go through it and I'll write down the concrete scenario.

G

You can just sit at this page few ones that is the work-in-progress one I shipped okay, just send me a link. It's like.

A

Links in chat and I also stuck it in the meeting notes, doc.

C

Cool now we have state or upgrade tests. So Reuben did you find something with regards to that? I began Debian packaging. That was not.

H

Yeah sorry I've been digging into that and I'm right now. My main obstacle is that I'm not super familiar with a testing framework and how things are set up so I'm, trying to big first try to figure how that part works before I keep digging into the logs and find out where it is I see something weird going on, but I first need to see how things are actually happening on the test side. So once that's you know, I want to have more familiarity with that area. I'll be able to provide more useful information.

C

Okay, yeah I can link here one PR that I sent yesterday. This was a pure system for bug, fix little girls drop liquid up greatest there and dress it up, but in general I hope.

C

Is that in general, I that upgrade tests will be greener, with with Jason's latest touch that should unlock it? That CD upgrade I'm gonna check manually on my machine if, if I can get an existing upgrade and if, if I can't or if I can there's probably something wrong with the packaging all set up in testing for, but yesterday it was broken for a call like for real as I couldn't get it working locally either, and that PR is now so now. The testing fraud technically should be working.

C

We'll talk to YX di or Jeff Crafton about the Debian company, see and I stuff.

C

Yeah I I think we're in a better shape than we were yesterday at least anything else. That needs to be said, or can we allocate some time for the cluster APs.

A

I moved dims as thing next, because it's kind of overlapped. What we're talking about which is you know, are we ready for the release candidate Cal, which is scheduled to be in eight days, I.

C

I

Just a query from the point of view of seek release, what what do we think is gonna cause us to move the date right. That's the kind of thing that we need to look at. Is there anything that we, it doesn't seem like from the conversation so far. There is anything, that's gonna block us, but then is there something that is likely to block us, and if so, you know how.

E

I

Be the next question or whether can we get through the release by documenting stuff and then when that leaves is cut, then we can follow up at the point of these. So that's the other option that we usually have I.

B

Think the biggest unknown factor is the upgrade test. Once we verify the upgrade tests are okay, I think we should be. Oh okay, I mean everybody's currently in debug mode kind of we're kind of firefighting me at this point, but I think we have a good beat and most everything that's happening right.

I

That's why I was commenting on the whip that that was there for collecting all the bugs. So we need to get them all in before we can look at the upgrade tests or any other tests to make sure that they're green right so.

B

I think I think by the end of the day, all those things should be merged. So by tomorrow we should have a good. We should have a better idea of a signal for the upgrade okay, so.

I

Today's the day right, yeah.

C

And also like now, getting the TD fix in that would just merge. I was really critical because otherwise, if we, if we hadn't, noticed that in time we would have had a problem, but with that in mind and Jason saying he had an successful uproot upgrade and with me and others that I'm gonna verify from latest master now I think we should have a or we have a way better signal. So that was that was the crucial, crucial part and we hope we have that under control.

C

I

Don't remember seeing a issue for the upgrade test failures that isn't the main cuban it is repository. Is there something that you need to surface from the q barium repository to the main repository? So you know we can take a look at it or oh yeah,.

C

Through through I'll open the the issue for like we, we often have an issue in kubernetes that it's like a cubed M team and release team issue. So we can coordinator like okay, we have five open issues in the Kuban repo. How created call all they can we move out? Can we all do then get need to get fixes like this today or whatever I'll open that issue? Today we have.

I

C

One one centralized point of communication between the release team and and the cubed M team other than slack. That is, as Tim said, ephemeral. Yes,.

I

Thanks a lot, Josh is a weird in darker console, I thought I'd. You know just ask the same questions that he would okay. Thank you thanks.

A

Next job, you don't talk about the cluster or API alpha status,.

J

Yeah, so for those that are interested in the cluster API, we've created a an issue which kind of sets the standard for which we will consider alpha, complete and so I encourage new one to like take a look at that. If you have interest or giving you feedback I, don't.

E

Know if anyone's taking a look at it wants.

J

To have any common right now, but yeah, that's that's kind of the place to to set the standards for what is in or what is out. The release. I think a leaks in the link for it is in the the doc do.

B

You have a time frame for when you want to in alpha. Is it gonna, be asynchronous from release or inline to release I.

J

Think, like time frame wise, it makes sense this July I, don't think we could hit all the miles all of the criteria in June and I'm, not thinking that we're associated with any specific release. I, don't know if Robbie has any thoughts on that yeah.

A

I mean right now we are are asynchronous with coverage releases. There is an outstanding issue about how we want to cut, builds and so forth that Chris Nova brought up on the cluster API call last week about whether we want to be tied to the main carriage release or not I think there are pros and cons, obviously cubeb, and currently it's tied to the main release, which has the upside of sort of giving you the forcing function of getting sort everything buttoned up for release and being able to be sort of blocking for kubernetes releases.

A

It also has the downside of being tied to the kubernetes release and I know that you know copses divorced from the carré's release, and that gives some more flexibility and so we're trying to look at sort of the different models of what we can do and talking to other folks in the community about what their plans are so filled with talk who is working. A lot on client tooling, has some some interesting thoughts about potentially breaking some of the communities, client tooling, away from the moon release as well.

A

So we certainly don't want to sort of skate where the puck is today. We want to see where the puck is going and think about how it fits in with other tools in the eCos and what their release cadence and cycle is going to be like so there's an open issue for that. I can link that here. People are interested in putting down thoughts for opinions on what they think. Good release, cadence or release cycle would be.

J

Okay, so I think that's that's all I had on that bullet point unless ever that agenda item, unless somebody else had any comments.

C

How, how close are we to be able to move our Cuba DME detesting to cluster IPR clusters.

A

That is a good question. We've been trying to figure out a howdy, it's alpha and then B how to start putting ete tests. On top of the cluster api, we've been reluctant to put tests on top it until it's at least somewhat stable, so I think. If you look at the issue, rob blinked and we and we burned down those outstanding issues, we'll feel like. We have at least a more stable core that we can start looking at porting tests on top of.

A

So that is something that is not on the very short-term roadmap because we don't feel like like we don't want to break people's end-to-end tests as we you take things in sort of the alpha phase, when the intent is to break things on our side.

A

One thing is to be a little more stable before it's the foundation for other people's stuff, where, if we make a breaking change that we have a rippling effect and and there's a lot of overhead to going and fixing all of those ripple effects at this phase of the project, so you know Robo saying maybe July we'll have alpha. If that's the case, then we'd look at starting to figure out how to rebase them in dentistry. After that, we.

B

Would happily be the first consumers of a testing apparatus just saying I.

C

So, honestly, like anything, you have now is probably better when we are what we have currently.

F

Yeah I mean the upside.

A

Of currently is nobody's changing any of the careers anywhere code right so that true.

E

A

That code aren't breaking you as a side effect right. So on the downside, is it's really hard to understand what it does? Yeah.

C

So the normal you do testing is pretty okay, it's been said, but dub great testing is harder and I think that when we want to do put this on top of gonna the cluster API, we should really have some kind of detail, doc and ambition before even starting to code.

C

So we we can really spec out the details and without having to go into like there's some binary like test and cube test or whatever it's called I, don't remember anymore, but like in that we don't have to build our stuff into cabinets bananas just for getting eatest EDD tests run, because that is currently the case. That is another more general problem as well.

I

Rob and wrong question was right. Now the Alpha criterias seems to point one provider. Are we going to have more than one provider for beta that we will list as a criteria or what is your thought process? I mean right now: it's vSphere and GCP right and I. Don't know how frequently how people are testing the vSphere. The one.

A

Yeah, that's a great question, there's a lot of folks in the community. That's that appear to be building other implementations so close to API call. It sounds like both Red Hat and hep.

A

Do we're working on a double yes, invitations, I, don't know whether the code for any of those are and I think would be great if we could sort of consolidate the code base for different providers and make that part of sort of the standard test suite so I think that's that's a great thing we should probably bring up during the meeting tomorrow is, if that's not an alpha, so maybe it could be argued that that should be alpha exit criteria all right now, it's on the list.

A

If it's not, should it be a beta exit criteria and if so, how do we have a path to get there? What.

I

We should do what we are doing for the top Florida, where we should say that there has to be a dashboard and it has to be integrated and they should be conformance tests showing up there the same stuff that we have for the floor right.

A

So assuming we put those those infrastructure pieces in place, if people are willing to contribute implementations on different environments, then we can put those in the dashboard. If nobody contributes those implementations, do we say we aren't gonna exit beta until we have those implementations right so I guess that is I. Think the question in my mind, yeah.

I

I mean how do you even know that the code ripple that somebody's finally doing doesn't the stuff that is required? Yes,.

A

And I think that's where, like the conformance test, but anyway yeah okay,.

B

Thank you. So you indirectly touched on something which I might want to bring up as an agenda item which is like the cloud provider documentation in integration for this release cycle.

A

Are you talking to me or the Dems.

I

I

You know before.

C

I then attended the cloud provider meetings for a while formula, a backrub cloud provider.

C

I

C

In general, sorry, please, you.

I

Ping me on at least three peers, where you change some some of the configuration options and all of them look good, but I have to try it out. That's what I mean. Oh you.

C

Meant that yeah so yeah so I was just thinking more generally, like it's really good that the other three cloud providers are going data in now in 111, I haven't tried one out recently. I tried it like here ago, something when we started prototyping, but not not. Now after I've just been reviewing some of the docs they have so currently we have two modes.

C

We have like entry you can set, and then you do cloud provider whatever set that are using API sub X drugs and controller manager, X drugs and in the cubelet extracts all these three exist in the Kuban in config file. So it's now like possible. Tsatsis use for the first time to use the entry cloud provider directly.

C

We are cubed M, so that is at least as good step forward in terms of usability, but we don't want to I mean we should definitely did document that, like you, can use these three string string all maps to like set the cloud provider, flags or components, but please check out the like out of three cloud providers.

C

Then now have like the conformance tests and stuff uploaded and run like Morris cube, see, they'll apply and an add-on on top of the cluster and Chuck said the other day here that you need to specify a cloud provider external to cubelets, and to do that, you basically have to give cubed M Joe in a config file with cubelet ex-drug setting cloud provider to external, and that is something we should should like document as well. That's this is standard.

C

J

Gonna say you can use the internal tree cloud providers using using an external like using cloud provider external on just the cubelet. Well, you've got a you've got a like set. The daemon set the cloud you gotta have the cloud controller manager running that points to.

B

The injury yeah so the the documentation is slightly maddening and by slightly it's very so the it's not very consistent and there's some alpha features that are called out in pieces that are kind of disconcerting for things that we are recommending for folks to use. So do we know if there's a single owner like? If do we have a single throat that we can choke to understand?

B

You know that who is the owner of this stuff, because it we're indirectly kind of touching all of this and I'd like to be able to have a single owner that we can reference that will give us the canonical source ensures yeah.

A

As far as I know, it's it's Walter fender, it's Jeff, taco on github is Lucas, has his hand up, but as far as I know he's the one driving from the Google side and I think his take over the driving from the folks that started the effort. Lucas did us um yeah.

C

So, like sick cloud provider has at least Django MacLeod or something as well as Andrew Andrew you Kim from digital ocean as sig leads I, think I'm, and then we have Sidharth Imani as well. So these are three people you can ping in sync la provider as they are leads. If you want to get some clarity into stuff, but like that for the more generic questions for then for every single cloud provider there is. There are a lot of differences, so then like if you.

B

Want to know something: it's fine if we point out to other documentation, it's just the the overall internal documentation and consistency of story and have have the breadcrumbs for a user to understand because right now like, if our user coming into the documentation, there's no way you'd have to like beautiful mind that sucker together to understand what's actually going on and how you set it up properly.

B

C

I'll ask Andrew about the state of Docs for for bida. I would guess that, like when they're going bead and now they have a higher like the docs, will be of higher quality as part of like the beta mark?

C

So so we could definitely do something there. But yes, as Chuck said the recommended way to do stuff with existing cloud provider cloud providers or to like run the do in initialize. All your cubelets with cloud provider equals external pass, the flag to the cubit start up your kubernetes cluster and then deploy with cube seeds. I'll apply, for example, the cloud controller manager that is, and that this binary, that is released by kubernetes and there's an image. There's everything like the normal cloud, the normal controller manager- and this is likely the stopgap.

C

So you can cube C to apply this binary for the existing cloud providers. Just setting cloud provider equals AWS or whatever and deploy that, and it will do its stuff and untain the cube, let's initialize them and similar. So that is like the idea that you can do this new flow using the existing cloud providers and when the existing cloud providers have broken out all the dependencies and all their stuff into a new repo, have a good release, process, etc, etc, etc.

C

You can just switch the image like a rolling upgrade like any controller any operator in the cluster you can just like do a rolling upgrade or deployment, and now you have a fully functional out of three cloud provider, so that is the like migration plan. Either you go in tree, set the cloud provider flag in every place and and similar or you go, are the three sets cloud provider external and all the cubelets and run the cloud controller manager or your specific binary like digitalocean, has something run your binary on top of the cluster.

C

That is the like short version, but I. Don't don't have the like last week's context of the exact state of if this is working.

C

But but if somebody like wants to like have a use case for R cubed M ducks, like just summarizes this, these piece of information, there are two ways: are they either you do this or then you do this, and here are the relevant, auto three ducks I would really just like to.

B

Have two like the single points like a pre step, two in it right like pre, step before you in it, you know think about your cloud provider link to the stock right so that that would be a nice just like punts. You know we don't want to face put to them and then they can maintain the tax properly.

C

I mean some like in the cross-cutting between the cloud provider and the Cuban stuff. This is how you, for example, this is how you configure an outer three Club, for especially for Cuban I mean that might be ducks weed way around, but.

B

Well, I'd like to live in time being because that makes more sense than trying to put it in the mainline docks and trying to hone that every time yeah.

C

In the reference section of Kibera.

E

There was so specific about specifics about the EWS the other day, a lot.

G

E

There yeah so the other question is: do we want to maintain this as a sick, because I mean we should just explain the genetic way how to set up a couple valid then the specific, possibly should be maintained by the coop provider. Six. We should.

C

We should do the general, but the problem is we get all the issues of people doing like I do cube at a minute with my AWS cloud provider and it doesn't work, is I, have another host name that AWS expects me to. That is like the second most common problem like you, if you incubate them so so we kind of get a lot of that and collaborating with with Sinclair provider and doing at steams at this kind of centralized place here are the cloud providers here?

C

Are the documentation 0 like the specifics of AWS cloud provider here or the specifics of the GCE cloud provider, and here are the docs for the big util ocean or OpenStack Club, or would be wonderful, but I, don't know if that is I. Think yes, I think so so before we end today, major teams.

C

Somebody wrote there already cubed I'm config, that is through Cuban I'm version 104 to to.

A

Be clear, you're, looking at major themes for the 1.11 release yeah to put in there.

C

Yeah, oh yeah, for.

C

For a cig for 111 release, notes myself and I guess Tim. If nobody else is gonna, do it Tim robot might may also want to put something there about the cluster API. Maybe.

A

C

A

We're divorced originally cycle I, don't think it's worth worth matching there. Okay,.

C

How about Justin anything like so now, I guess we would talk about cops 110 then, but anyway, it might be worth adding something.

F

Articulate thank you.

C

Qing Yi on the docks yeah, so with regards to Cuba I am wishing one of the two configuration new stuff there or cubelet cubed M, now kind of controls, the cubelet using structured component config lots of bug fixes. Yes,.

C

Is there something else and try it.

E

We should probably mention one of those things that we oughta made stuff: what cube ADM in it time for the cupboard like the release.

E

So the the secret driver and the resolve the issue yet I.

C

E

C

That falls under lots of bug, fixes.

B

To the configuration mechanism.

C

Yeah yeah both of those but score DNS, could be a good thing to note that so cubelet securities and add one actually, we could say cubelets configuration and yes, because what we do now is like. We have a breaking change in the sense that we disable the read-only port, for example, to be more secure and and stuff like that.

C

Being the forerunner like what the cubelets is going to have as default.

C

We have the new cubed above grade diff command, but maybe not a team. It's it's more like specific feature.

K

E

Well, I think we should list all the new commands to be on that.

C

Is also all the new commands, it's gonna be like multiple levels: we're gonna have major teams. First, major teams for all the SIG's, then a lot of action required stuff with PRS and and similar, and then, after that, we have like individual SIG's, also relevant what you need to know about PRS so like the PL that adds new commands will will be listed there, that changes, behavior, etc. So there's gonna be multiple levels of granularity there, but neither config file controlling the cubelets Gordian as default.

C

Lots of bug fixes and new CLI commands.

K

Might be changes the meaning it workflow and is something that should be highlighted that because many people are using coubertin's in an urban environment. So this is a sensitive topic for them.

C

Yeah I mean it's it's better now, but yeah we could. We could like in general, like a major team, for that would be like making cubed M.

C

Work better with other CRI runtimes and like in and air-gapped environment environments. Maybe that would be a major team. I can see because it all like this towards I go okay, I I think the time's up robots. Yes,.

A

I will just mention that it's now 10 o'clock. Thank you, everyone for joining. We will see everyone again next week right before rc1 gets cut.

C

We have a cube in our offices today tomorrow as well. I think yes, as well as the class area yep, take care bye.