VMware Tanzu Community Edition Community Meetings, 13 Apr 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Tanzu Community Edition Weekly Community Meeting - April 13, 2022

Description

Tanzu Community Edition Weekly Community Meeting - April 13, 2022
We meet every Wednesday at 11am PT. We'd love for you to join us live!

This week we discussed our upcoming talks at KubeCon Europe, v0.12.0 release updates, and John McBride demo'd unmanaged clusters. See full notes here: https://hackmd.io/CiuO4V0AT6WL_TgA47MXBA?both#April-13-2022-Agenda

A

Hi everyone welcome to this week's edition of the tonzu community edition weekly community meetings. Today's date is april. 13 2022..

A

If you are watching this from home as a recording, we would love for you to come and join us live we meet every week on wednesday, 11 a.m. Pacific time. If that doesn't work for you, we also meet monthly held every second thursday of the month at 9. 00 a.m. India standard time- and these are just opportunities for you to come and meet the maintainers. Listen on what we've been working on, provide feedback. Ask questions.

A

You can also just sit and observe you don't necessarily have to engage with us. We would. We would still love to meet you and have you participate and join in the community. So hopefully those options do work for you, but if not, there are other ways to reach us. You can find us in the kubernetes slack workspace in the tanzu community edition channel. You can ask your questions on the github discussions.

A

Add your requests or a question or suggestion to our issues list. You can email us in the google groups, email address or you can find us on twitter at vmware tce.

A

If you do have something you want to bring up with the team and you want to participate in one of these meetings. You can add that to the discussion topic section of the agenda for the date that you will be joining us and that's just down here at the bottom and once we get through all the other stuff, we'll get to your question and we can have a discussion about it at any point you are interacting with us or any members of the community through any of these mediums.

A

We ask that you please read and abide by our code of conduct, which is here and it links out to our repo.

A

For those that are using tonzo community edition, we would love to know more about how you are using it. So we've created this pinned issue asking for a few details about yourself and how are you using it? So if you could, please add those details in a comment, add a png logo, a version of your logo. If you wish to be added to a doctor's file, it's not required, but we would love to showcase those organizations that are using tanzu community edition to to show other community members who all is using it.

A

For those who are in attendance today, please make sure to add your name and the company that you are representing to the attendees list here and on to announcements.

A

So for uh for content, wise we've added a few different things here um we have kubecon platinate of con europe coming up as far as events goes where tons of community edition folks are going to be. We have several talks that are part participating in either kubecon or related events. In valencia we have david, who is one of the tomsu community edition maintainers, he's doing a talk on may 14th learnings from creating ci cd pipelines for open source kubernetes projects.

A

We have the corbs delivering a keynote at k-nativecon on tuesday may 17th, and we have john mcbride who's.

A

A tons of community edition maintainer delivering a talk on wednesday may 18th the risks of single maintainer dependencies because he's also a maintainer of another project so be sure to look at at that and see more details about that, and we have myself delivering a talk at kubecon on thursday may 19th, talking about being a community manager and all the crazy nuances that come along with that, and I will be doing that talk with my co-speaker karen chu who's community manager for helm, and then we have talks by stephen wong, who is also working on tons of community edition, and he has two different talks and a few I think, a few others in the works.

A

So I put just a link out there to his talk. So if you would like to attend either virtually in person, I believe all these have those options be sure to click on that go register.

A

If you're there in person come say hi, we would love to meet you and know more about you other opportunities to see us at these events. We will have some booth presents at kubecon, but stays tuned for more details on that. We're still ironing out everything, and then we also want to do some sort of um you know informal get together whether it be like just having lunch together at the conference set up, we're not really sure yet, but once we we have more details on where we'll when and where we'll be.

A

You can just come and say: hi hang out, um you know just get to know each other. We would love to to meet everybody. That's gonna be in attendance, so really excited really looking forward to that hope to see you there.

A

Next up, we have webinars so upcoming webinar. We have something coming up tomorrow april, 14th at 10 a.m, pacific time, speed up delivery with modern software supply chains and vmware tanzu community edition, that's when jennifer kotson, corey, cora, iberclade and bina moore and so just be sure to click on that and register to attend.

A

We also have a blog post that was posted a few days ago by stephen palsde, comparing manage and unmanaged clusters on vmware tanzu community edition and then, as far as the next announcements go, we are working towards a may 10th release date for 0.12. and with that, let's move on to status updates on that particular release.

A

So for engineering updates josh, you want to give it a whirl.

B

Yeah sure um so we'll do just a quick overview and then john's gonna give a demo so, as you've heard we're targeting, may 10th probably have rc one next week. If all goes well. Some key things in the core that are happening is there'll, be some small updates to our bill of materials. You'll see kubernetes 122.8 in this release. um You might also be aware of some scd corruption issues in the version of ncd we've been using, and this will be mitigated in this release.

B

The framework version, if anybody uh plays around under the hood with tanzu framework, will be on a framework version that is v011.4 and then outside of that there will be a bunch of enhancements to unmanaged clusters. We're going to have a new feature called profiles that john will show a new provider that john will show.

B

We are introducing start and stop lifecycle hooks where you can stop us cluster and start a cluster, some cool stuff, where we can provide updates to our bill of materials. So, like kubernetes versions and package versions dynamically, we call that dynamic tkr resolution, that's kind of the fancy name for it and then probably the only thing that we had talked about doing that's at risk and might not happen in this release is right. Now our default cni for unmanaged clusters is calico.

B

um There's some latency in some of the package stuff we're trying to update and some small little uh issues we're hitting. So we might stick with calico in this release and then move switching back to andrea as the default in unmanaged cluster in v013, andrea will still be fully available. I mean you can still set it as your cni. It just might not be the default for this release um and uh kartik, I noticed you're on. Is there anything before john gives us demo? You want to talk about with these app dev enhancements.

C

uh Yeah, just uh just quick sort of the purpose of these uh enhancements, one is around the app cli just there's a way to interact with uh what is going to be called the. What is known as the workload object uh that comes from cartographer, um so the app cli makes it uh sort of intuitive for an app developer to interact with various operations, as you would, with a workload creating seeing the logs or getting you the url and so forth.

C

The basic supply chain is it's actually. I should rename that to be called cat cartographer catalog it today in this release, will come with like a basic supply chain pattern um that gives you an out-of-the-box way of uh using cryptographer with going from sort of source code in your gate report to a canadian service. So it kind of describes that pattern and can be the basis for any customizations you may want to do. um The third one um is what is known as the keypad dependencies.

C

It kind of helps you bootstrap uh cluster store, stack and builder, which are the resources you may need to like be able to build images. um Yes, the uh scott cartographer will be updated to the o dot three release uh in tce. I think that pr is uh currently in review from nick so yeah. Those are all the kind of enhancements that are coming.

B

Awesome and then that's it for us nancy. If uh now would be a good time for john, we can see a demo of these cool new features.

A

D

If I could get the screen here, we go all righty, hello, everybody. uh This is going to be a demo of unmanaged clusters mini q profiles. Oh my uh there's so much stuff coming in v012 for unmanaged clusters, but we want to focus on the new mini cube provider and specifying profiles on unmanaged cluster bootstrapping. So these are new features coming in v012, v0120 and first up is the minicube provider.

D

I think most people uh in here probably know what minicube is uh for those that don't it's a way to quickly get a local kubernetes cluster uh mac, os windows and really its focus is on learning and development for kubernetes itself. uh What makes it really really powerful is that it has a ton of different drivers and ways that you can deploy it so vmware even has their own driver for vmware workstation, there's, obviously docker kvm, it's great.

D

So this gives people deploying unmanaged clusters with this provider a ton of different ways to deploy to different types of container runtimes and virtual machine managers so very exciting. But why tell when we can do so? Let's do a mini cube demo here. Let me get over to my terminal, uh so quick. Let's look at tanzu unmanaged cluster.

D

Let's see what version we're on uh just a quick note. This is a patch that I made this morning, there's a pr for a couple of the config options in here. So if you try some of the things we're going to be doing off of maine today, you might just need to wait for the release, but this is kind of the experience as it exists today. So first up uh mini cube can be accessed through the mini cube command line.

D

uh Let's just take a quick peek inside of there to see what current deployments are on here and that is via the profile list. uh Also of note, the word profile is a bit overloaded in this demo.

D

So in the context of minicube, a profile is basically a cluster or a deployment within what minicube knows about there shouldn't be any profiles, there's no minicube deployments because I cleaned everything up earlier. So let's go ahead and just fire right into it. We can do unmanaged cluster, we're going to create we're going to call this mini test and then, with the provider flag, we can just say mini cube, and that is going to get going right away.

D

Also of note here, we can see this. This chunk right here, which this is actually querying. A compatibility file uh josh had mentioned that as part of the feature as well, but that compatibility file will make sure that this deployment uh with a compatible tkr of this version of the cli. So that's just a little preview of that deploying right there. uh It's selected a compatible tkr, this v0170 dev2, and it it's off to the races with mini cube, deploying right here.

D

So this will take just a little bit longer uh because mini cube deployments just take a hot second longer versus uh uh versus kind. So, if there's any uh intermittent questions, we can answer those okay, the cluster is created, it's already started to install cap controller and for those who maybe are joining and are unfamiliar with what unmanaged cluster is.

D

If we like, really kind of take a step back unmanaged clusters, a way that we provide to generally give a local cluster that is kind of tanzuified, it has cap controller on it and it will have the package repository and all the packages that then you can install with tanzu package. So we'll take a look at that as well, so yeah feel free to ask questions in the chat or raise a hand or interrupt anytime. While this is going. This should just be another second longer so right now.

D

What it's doing is it's installing the core repository? It's reconciling that we can see that is happening.

D

Yeah, this is gonna, have a little bit of a little bit of a pause, but that is just a-okay all right cool that wasn't too bad. So that finished uh we can do that same command, uh inspecting into mini cube, which we can think of as kind of the next layer down it's the actual provider which sits under unmanaged cluster. So let's just take a look at their mini cube profile list and we can see our profile mini cube test right.

D

There is running awesome, uh so let's use a utility that I, like called canines, which just kind of gives us a fast graphical user interface to fly around the cluster. Let's look at the pods, those are initializing. Those are running. We can also look at. Let's look at the package. uh Let's look at the packages and kind of like I was mentioning. This is all the packages that exist in our community package repository uh and then we also, if we scroll down, we can see the tkg system ones. These are the core packages.

D

If we look at package installs, this gave us the cni, which is the default uh calipco cni like josh mentioned, so uh that is just the most basic way of doing this. We can also tame zoo, unmanaged cluster ls and we can see the mini cube provider and it is running uh kind of like josh mentioned the start and lifestyle the start and stop life cycle hooks are now available.

D

uh Let's just take a peek at those a manage cluster we'll just say help and we can see start and stop that will kind of inspect into mini minicube or kind or whatever provider. You have and do the start and stop for that cluster. We won't do that right now, but that is available.

D

So that's the most basic option: let's, uh let's delete that cluster now image cluster delete mini test and that deletes uh pretty quickly within seconds.

D

uh So now, uh let's do a more interesting, slightly more complicated, ish uh demo here. So let's do tanzu unmanaged cluster config and what the config command gives. You is bootstrapping, a config file that you can then feed into the create command a little bit later. So let's do config and let's just call this uh mini test. I think actually, I already had one in here so uh tanzu and manage cluster config mini test, uh and then, let's give this the provider, just like you would with create so provider, we're going to say, mini cube.

D

This might fail because I already have mini tests. Rm mini test. Try that again provider mini test. Okay, so that's going to write our configuration in yaml file right there uh and we're gonna vim mini test. So this is just the config file that it basically spits out uh with all the options that you can configure to create. So, like josh said start in mini cube a cluster, so we can see here, provider is minicube and then we do have this provider configuration with which gives us specific options per provider.

D

So one of the cool ones, like I mentioned is we can specify driver. uh So let's do driver uh not like that. I know how to gamble uh driver and it's uh what I wanna use is kvm and what kvm is is on. Linux is a kernel-based uh virtual machine manager, so this will be right.

D

On top of my linux box that I'm ssh onto kind of bypassing docker and then we can also specify the container runtime so container runtime and we're going to say container d so instead of using docker as the default container runtime we're going to use just right away container d here and then I also let's say that I want to specify something really unique like something that mini cube. You know provides way deep down in some config flag.

D

I can give raw uh mini cube, args and, let's just say, I want the disk size to be a little bigger. So let's do disk size. Let's just go something like that.

D

There we go uh cool so that will build the kind of uh list chart. uh Excuse me does that need to be a list for mini coopers. uh No, so this is. This is just a.

A

D

It's a big string, yeah, it's a big string of bark. So let's say I wanted like oh cpu, you know something something yeah. It would just be a big long list of arcs yeah, so it kind of takes this. uh This string and just plops it right into a mini, cube command and interprets those, as is so uh yeah great question great question.

D

So uh kvm we've got container d and we've got a custom argument in there, uh let's quit out of here and let's use that uh in a tanz view, unmanaged cluster create so just file minitest.yaml, and we can see right there and that warning that it's reading the provider configuration some of those specific flags may be ignored and or used. So that's just kind of a general warning for using the provider configuration that's going to take another hot second uh yeah. Any other questions. I guess. Oh josh loves the qmu and kvm this.

D

uh In my experience deploying this, it just takes just a little bit longer uh since it's bootstrapping, a virtual machine, so um yeah feel free to make comments or talk amongst yourselves.

B

Hey john, uh can users use like kind and mini cube, or do they need to pick between providers as they like spin up and down clusters.

D

uh You can mix and match do both uh the default will be kind. So if I just did this create command and give it a name, it will make a kind cluster. uh If I did another one and said tactac provider mini cube, those would live right next to each other. uh As far as unmanaged cluster c's, so yeah you can do both.

D

Does that answer your question? I think I understand cool cool okay, cluster created. uh You know why don't, while that's happening, let's uh create a side-by-side terminal, uh let's mini cube profile list again and we should get oh. That is gross. uh Let me exit that let's do nope not that way. Please hold okay. There we go that'll, look better mini cube profile list and we can see this is running on kvm with the runtime container d.

D

uh Yeah, there's a bunch of these options, so I really recommend people curious about this or unfamiliar with minicube itself to go through the documentation. Look at the different drivers look at like all the different things that are possible uh yeah. It's really really cool and exciting. Okay, so that is done. uh We can come in here. uh Let's go back into, uh let's see, canines, take a look at everything, just real quick again, and a lot of this is the same. So this is uh the package install with calico.

D

Let's look at pods, uh all that is bootstrapping. Let's look at packages and there's all the packages, so this effectively is a unmanaged cluster on top of kvm with container d runtime very, very exciting. So I think that was mostly what I had for just looking at my notes: okay, cool. So uh let's get out of this and go back into keynote uh any general questions on the mini cube. I guess time for questions at the end as well, if not all right cool.

D

uh So next up. Another big feature coming to unmanaged clusters is the idea of profiles again a bit overloaded uh name pending uh profiles is also something that tap uses the application platform, so this name is kind of in the ether right now. This is just what we went with during development, but essentially what you're getting here is an automatic way to install a package from an installed packaged repository, and you can provide a special syntax here to get the specific package by name uh by version and or with the package yaml's value yamls.

D

So uh what this gives me is you know any of these that I had installed in the package repo fluent bit: rafana external dns, app toolkit.

D

Any of those are then automatically installable on cluster bootstrapping, so right away in that create command from unmanaged cluster uh so again, best way, let's take a peek at this come over here.

D

Let's quit out of this, let me just quick clean up again.

D

And that should delete that in just a hot second uh scott said, so we can deploy a tap profile if you hit tc profile on a mini cube profile, yeah yeah naming is hard, uh but we will we will overcome. We will get there. So uh what I want to do is I want to uh just do the most basic example: let's do tanzu unmanaged cluster and manage cluster, create I'm just going to call this test. uh Let's not provide a provider right now.

D

Let's just do the default kind uh and what we could say is profile. Let's just do fluent fluent bit. It can be the fully qualified name of that package or just a snippet here, and it will detect uh that that package by name. So, if I uh do this, it will do the latest bloomber package with no values. This is just like the most basic install. uh I'm not gonna, I'm not gonna fire this off, because it'll take another hot.

D

Second we're running a bit short on time, uh but this will give you fluent bit automatically installed on your cluster at bootstrapping, like very, very cool. Let's do a slightly more complicated example, actually with app toolkit, which app toolkit is interesting because it's it's a whole bunch of packages, all kind of meta packaged together in a big thing that then all gets automatically installed via profiles on the unmanaged cluster. So I have a config file here.

D

uh It should be app toolkit.yaml, and this is really just the most basic thing for a local install here using cluster apis uh cluster. Ip excuse me, let's quit out of there, uh and we can use that value yaml's file uh with our profile unmanaged cluster. So, let's create uh we're. Just gonna call this test profile.

D

So what I want to do is app toolkit which will select that name by this prefix, uh and then we can also specify latest here as the version uh that's a keyword inside of this special mapping, which will get the latest version for that package. So uh I could also specify uh 1.0 uh 0.1.0, uh which is the latest one, but uh latest is just easy.

D

So then that uh yaml's file was called app toolkit.

D

I believe, and uh we go off to the races and it will start deploying that first bootstrapping, the kind cluster which is really not the most interesting part of this. uh It's another comment from scott will only auto complete the full package name for tcd packages, with this specific tce suffix or any package added via the additional package repos. uh That is a great great question: scott. uh Yes, it will work with additional package repos.

D

uh I thought about putting that in here as well, but for the sake of time, for those that don't know, we also added the additional repo flag on top of create, which gives users the ability to automatically install a package repository uh via the url of that package repository. So so, yes, you could use additional repo to install a package repo and then use a profile to automatically install the package from that new repo that you had automatically installed. So uh the chain of kind of installation would be your custom repository.

D

It then looks and sees that that name is in that repository and then installs that profile uh but yeah. That would definitely be a really really interesting use case for sure.

D

Okay- uh and you would see that in this step, so in this step it's reconciling the core repository and then it will reconcile the yeah this project's registry, our community repository and then you would also see it reconciling uh your additional repos uh uh repository here uh after it does this reconciliation, it selects it selects the package, and we can see that it did that right here, so installing a profile app toolkit, it selected this one using profile version that with app toolkit yamls, let's look at the canines again and let's go to pods and a bunch of this uh starts coming up.

D

uh It takes a bit of a minute. It looks like carcartic dropped but uh yeah all this starts coming up and automatically using our animals file with those values. So if we go to package installs, uh we can see app toolkit here uh and then it is reconciling all those that are part of app toolkit as well, like sort manager, flex, cd, all that interesting stuff. uh I think I will actually uh am I good to go to 12 45 or what's time on this. These days we went to 45 minutes on these right.

A

Yeah, so we have um yeah a little less than 15 minutes.

D

Okay, uh what I would love to do quick is actually put this all together. I think scott even said something about you know installing a profile on minicue profile, but I would love to put this all together uh via a config file. So let me again it just clean up real quick, let's ls, uh that kind cluster is running, tanzu, unmanaged, cluster, delete test cool and that will get rid of that. So let me come back into my mini test.

D

Yaml file- uh and this is you- know the provider configuration on kvm all that uh we can specify these profiles uh as a list here in the profiles configuration uh so let's slap a few things in here and and see what happens so, uh let's just do kind of, like I had said before, let's do fluent bit, uh let's also do like I had before app tool kit uh and we can provide the fully qualified name to select exactly that one in case you maybe had a little bit of an overlap with the pre, the prefix name uh like if you were adding an additional repo uh and then we can provide the config and that was app toolkit.yml again, that's uh relative to where you deploy so uh be mindful of that.

D

uh So this config file now actually has quite a bit going on. We are doing minicube provider with provider configurations and we have specified two profiles both fluent bit and app toolkit. uh So if we save and quit this, we can tanzania manage cluster, create file mini test and again that is off to the races.

D

So, first it's creating the mini queue. Cluster then we'll see it reconciling the packs repositories and then it will reconcile those profiles which again will take a hot second.

D

uh Scott asked: does it wait for a package profile to reconcile uh excellent question? uh It actually does not, so it adds the package install onto the cluster, which then cap controller can pick up and start reconciling and adding the actual. You know pods and all that stuff, but we do hand back the cluster uh to the user, and that was a pretty deliberate design decision just so that if there are problems you can see those problems uh debug those problems, and it gets us to the next step in this flow of setting the context.

D

That's that's really useful, uh even though we do have this, uh this q config right here, uh we felt that you know at the end of bootstrapping. The cluster is pretty much up. uh It's just maybe not reconciling the profiles or those packages or something instead of having the user have to like go find this cube. Config file just hand the cluster back to the user. Do the context uh merge and then it's right there ready on the command line, and you can start you know looking at stuff and debugging stuff, um yeah.

D

Definitely open the feedback on that. uh If that's a user flow that uh you know it doesn't make sense or or uh doesn't work for you, but yeah, that's an excellent question and we kind of saw that with app toolkit in the last example where uh app toolkit can take, you know a minute to reconcile, uh but after these package repositories are ready, it pretty much just installs the package install like we'll see it right here there goes there.

D

It goes uh installing profile fluent bit installing profile app toolkit, uh and we can see a few warnings here where it's saying: okay, I'm installing the there's no version specified. So I'm going to use this one, no configuration file. uh We didn't specify a version in the config file here, so it's just using this latest one. uh It will try to select the latest one, uh but if we go into canines uh we can see let's go to pods zero. All this is coming up still so these package, these packages actually haven't reconciled.

D

So if you go to package installs, uh all these are uh where it's reconciling my zoom windows in the way yeah. So, on the right there you can see those are all still reconciling yeah, excellent question: uh nice choice to set context and give control back to user yeah. We felt that that was that that was a good workflow um scott said, would love, maybe a flag to say, wait for profile yeah? That's a great! That's a great suggestion. Wait for reconciliation yeah!

D

That's a great that's, a great suggestion, because there could be use cases where in like you, know, you're deploying something, and you have some like automation. That is waiting for. You know contour or kpac, for something to be up right within the uh the app toolkit suite of tools um but yeah. That is all that's going to start coming up. We can watch that uh that was it for the demo. uh Any additional questions, thoughts comments concerns.

D

I can go back to pods too, take a peek at all. This.

B

Yeah john, I think just to scott's point as well about being able to disable the wait for profile. Is. um It might just help as well with the developer experience of uh creating new profiles or, if there's a problem with the profile, because then you can get access to the cluster, even when the profile doesn't reconcile properly.

D

What is um I'm blanking, maybe nick can can comment, but uh what is the current behavior of tanzu package and install? Does that wait or does that keep the cluster back? It waits it waits okay yeah. Maybe maybe we need to kind of smooth out that ux edge. uh If there's, if there's a difference there but yeah, let's create an issue and yeah. We can definitely follow up on that in another release. For sure.

E

Yeah, I think, having a flag, I think it makes sense the default that was set of not waiting for unmanaged, but I think that having the ability to wait for like in ci cd or any other automation that you would want to spin up, a cluster have, let's say app toolkit installed, and only once it's installed to continue.

E

Instead of needing to pull yourself the status of the package have that be part of the bootstrapping itself, you get it back. You know you have a working cluster, you can start working on.

D

Yeah I'm totally following yeah. I can. uh I can make an issue for that. I think I I definitely understand my workflow for sure.

A

Any other questions comments.

A

John thanks for for doing that, it was an excellent demo.

A

All right we have about five minutes left. Let's take a look at the agenda: okay, shimon. You got some updates for ux stuff.

F

Yeah, first again, john great demo, uh I'm basically filling in for justin, with an update on the guided ui plug-in that we're developing, um and these are basically three uh points as to where we are we're continuing to refine the mockups for the welcome screen and the simplified workflows.

F

We've done the aws one now we're doing the other providers, we're exploring the ux and apis are on the workload cluster creation, which is, of course, the second step after the management, cluster creation, and then we're also doing so. We've done some scaffolding uh for the tech stack that are in place. Building out. You know areas of the ui uh where the mockups are complete or almost so any questions on that.

A

All right thanks, shimon moving on to discussion topics, looks like we still got about five minutes left, uh so someone put in included software in cap controller 0.35 joe, is that you.

G

That was me sorry. I didn't I forgot to put my name, uh but you know just because the this team had the there had been an ask originating from um tze.

G

So I wanted to both like make sure we we closed the loop and the the latest cap controller is a pull requested into u-hauls repo and for a little selfishly from my end, I'm I'm kind of curious to hear how this fits into um uh like how this is gonna get used in in tce.

B

Yeah I could uh I could take that one if it's helpful, um it's a little bit of a more complicated answer than I wish it was, but how it currently works today is that you're bringing in the upstream source for a package in this case cap controller and the direction tc wants to head over time- is that we pull in that upstream source directly.

B

So, like your thing gets merged and ideally that cap controller we'd be bringing it into this next release and talking about it for a variety of technical reasons, we have to stay bound to the same version of underlying components that tkg ships with this won't be this way forever. But it's the way it is right now.

B

So in summary, there will be some latency wherein you've brought this in upstream it'll, eventually get slurped into a tkg release and by the way, for those who don't know, tkg is vmware's product, tanzu kubernetes grid and then once it gets slurped into that it will be in a tce release. So, um in summary, probably in like the era of like v013, which will be our release after this upcoming one, we'll probably see a bump like this in in cap controller, did that answer your question.

G

um I I think I I guess I was hoping specifically for the included software, where it's it's kind of this, like it's, not an s-bomb, but it is it's like a a bill of materials, light feature that allows packages to indicate like optionally what what they've what's included in them. um I I was wondering specifically with that feature. What's the what the use cases are uh in in tce.

B

Oh sorry, I misread your question completely. um I'm not entirely sure offhand. I don't have. We had s-bomb uh desires come from the tce team.

E

I think the main one was around app toolkit where, because app toolkit is a meta package, that includes sub packages was a way on that package to say what packages it includes to say. We include within this single package, this version of kpak, this version of contour. That was what was in the original issue.

E

That kartik had also opened to be able to say what version of the app it is and also came up from cube, apps's side, adding in the package to say how can we differentiate like the chart, chart version and app version you have in helm into a package um in order to get kind of the versioning in those two levels for the cube apps package in pc as.

G

Well, cool! Thank you, scott. uh As is often the case excellent tons of repository. uh uh We should give you a title: you're, the you're, the tanzu knowledge repository. Thank you.

A

Any other comments.

A

Okay, all right! Well, thanks everyone for joining this week's edition of the tonzu community edition weekly community meeting. um If you're watching this from home, we do hope you join us at the next one. We would love to meet you and and get your feedback and and um have to like be able to help with anything. You may have um needed with the tce stuff, so that thanks and have a great day.