Welcome everyone. Thanks for joining us for a special edition of today's CNCF live webinar, Kubernetes version 1.26 release. Some exciting stuff coming your way. I'm Libby Schultz and I'll be moderating today's webinar. I'm going to read our code of conduct and then hand over to Leo Paul Kay, Fred Munoz, and Mark Rosetti from the Kubernetes 1.26 release team. A few housekeeping items before we get started. During the webinar you are not able to talk as an attendee, but there is this lovely chat box that everybody is adding their hellos and locations to. So thank you. That is where you can leave your questions for the team. We'll get to as many as we can at the end or if it so pertains, we can interject in the middle. But we're going to have a full webinar today, so be sure to leave your questions here for us. This is an official webinar of the CNCF and as such is subject to the CNCF code of conduct. Please do not add anything to the chat or questions that would be in violation of that code of conduct and please be respectful of all of your fellow participants and presenters. Please also note that the recording and slides will be posted later today to the CNCF online programs page at community.cncf.io under online programs. They're also available via your registration link used to get here today and will be on our online programs YouTube playlist. With that, I will hand it over to our release team, Mark, Leo and Fred to take it away. Thank you, Libby. I'll take it from now. Well, let me start to say that it's a huge honor to be here and be able to present the major updates of Kubernetes 126. I think in our independent opinion, one of the best releases of Kubernetes so far. And let me start by presenting the team. So obviously we have our 126 release team leads Leonard Parker from Liquid reply, which led the entire team in terms of the 126 release efforts. And Mark Rosetti from Microsoft, which was a part of the 126 enhancement steam and it's the key and currently is the enhancements lead for Kubernetes 127. And, and I, Frederick Munoz from SAS, which, and I was the communications lead for Kubernetes 126. And we have a interesting, although not completely original agenda, because we tend to follow the same major approaches in each Kubernetes release to share with you today. So we will start by providing a status updates on the 127 release cycle that started very recently. We will then go on into focusing on some of the major highlights, removals, applications and aspects that we want to really talk about in terms of Kubernetes 126, including the major teams, etc. And then we will go through a per se lists and description, quick description obviously given the time constraints that we have on the enhancements that were not only track but implemented during this release. In the end, we will give a quick description of the release team shallow program, and we'll hopefully end with plenty of time for any question and questions and answers from our side as needed. Oh, sorry. Can't you hear me. Leo and I can hear you but I wonder. I can hear you. I wonder if other attendees cannot. Okay, perfect. You can't hear maybe leave and rejoin us. Okay, so. Excellent. Glad it's not. On my end, because sometimes it happens. I'll, I'll, I'll proceed them. I think with some updates on the Kubernetes one 27 release cycle. As you are likely aware, Kubernetes has several releases a year and just when we end one another one starts and the cycle continues. Currently, we are on the Kubernetes one 27 release, which has the following timeline it started some weeks ago in the ninth of January. It will have the enhancements for freeze on the 10th of February code freeze on the 15th of March, and is scheduled for release on the 11th of April. And it will be released to Kubecon here because it will follow very shortly after the release Kubecon and cloud native con Europe will start on April, April 17 and 21. So, this Kubecon will be will be made in in the footsteps of the 127 release. Currently there are no changes in terms of the plans timeline. Changes do happen in the one 26 release cycle, for example, we did have some slight adjustments to accommodate the security updates and go. But the process itself is made with this in mind so there are the necessary leeway in place in order to avoid making any potential rescheduling an issue. And with that, I would, we will now go into the Kubernetes one 26 highlights major team changes were over the deprecations. And there's nobody better to be able to provide this to us than Leonard our release team beat. Hello everyone so you could go to next slide. So every release cycle we have a theme so the release team has a name and the logo and a theme of the release. It does not need to have like a, like a special meaning. So it can also be just a joke or anything like this. For this cycle, we've been a little bit more, more, maybe, I don't know, we had like a little bit more thoughts in mind with electrifying in terms of environment. So we want to raise awareness that Kubernetes clusters are deployed everywhere, powering huge systems, and therefore also like requiring a lot of energy. And this is at the moment in the caps not being reflected as much. So this might be like a big theme or major theme also in the future for this cycle, unfortunately, not. But yeah, we want just to raise awareness. And I hope you also like the logo. There will be some, some stickers at KubeCon if you, if you catch me. All right, for the enhancements, we track the cycle 49 enhancements. So depending like what you count as an enhancement, we also count removals and deprecations. So if you break it down, we have 11 stable ones, 10 beta ones, 16 alpha caps, nine removals and three deprecations about the stable beta and alpha features. We will talk about them in the updates in a bit about the removals and deprecations. I believe this is the next slide. I know this is the one after that. Okay. First, for the major themes, because we will discuss every one of them in like a little bit more detail, like on a slide exclusive sites, I will just like run it down so you have like an overview, like a teaser of what we will discuss this the rest of the session. So first, we now use exclusively registry.khs.io. This was broadly discussed in the past we use the GCR registry. Now we just publish new artifacts registry.khs.io. So if you use, or if you pull the artifacts manually, you now have to use a new endpoint. We now graduated designing artifacts to beta. We support now or graduated stable privilege containers to stable for Windows. We have some in hand, like changes in the CS migration, which is a larger effort. Now, we also include Azure Fights and VS Fair over like external plugins. We delegated the FS group to CSI drivers, which is now stable. There's some changes in the metrics framework. And we added some changes to component SLIs, some feature metrics. We have a very big change with dynamic resource allocation which introduces a new API, which is very exciting. It's an alpha and we'll graduate to beta and so on later. We have a cap focusing around admission control. We have one alpha feature for bad scheduling readiness. Made some changes for node inclusion policy for topology spread, which graduated to beta. And node graceful node shutdown graduates to beta as well. As I said, we will discuss them separately, so I just want to go over them quickly so we have more time. For the removals and deprecations, the first one removal of the cube proxy user use space modes. We deprecated the user space proxy mode for over a year. And now it's no longer supported on either Linux or Windows, so we removed it after it was deprecated. The next one deprecations for cube API command line arguments. So there's a flag, the master service namespace command line arguments do not have any effect anymore. And it's basically already deprecated, but not officially. So this cycle, we now officially deprecated it. So in the future, we can remove it, which is like policy and Kubernetes. The next one removal of the V1 beta one flow control API. We remove the flow control API server dot KHS dot IO V1 beta one. And now you need to migrate over to V1 beta two if you want to use it. So this has also been deprecated before. And the V1 beta two is available since 1.23. So there's like a good chance that you're already using that one. For the next one, under sick auth, we remove removal of the entry credential management code. So this cycle, the legacy vendors. Did we lost you? Suspenseful. It looks like it. Yeah, I think a couple of seconds. Unless you didn't notice and we will only catch him in 20 minutes, but I think that he will join. Otherwise, I can pick it up or marks. Do you want to? Oh, you can pick it up. Okay. So we were on the entry credential management codes. Essentially, this is not completely unlike the CSI migrations and that's there. There is internal logic that was contained within the Kubernetes code that dealt our specific cloud providers. They had the credential management and this has been externalized into plug-in. So it's being removed from the entry source. The removal of dynamic kubelet configuration group is a slightly different reason. The removal following the policy that when there's not enough uptake and essentially enhancements don't progress into stable. After a while, they get dropped because they aren't used as much as initially taught. In terms of figure out of scaling, we have the removal of the V2 better to horizontal part of the scalar API, which not unlike flow control one means that there's a need to update to the updated version of the published horizontal part scalar API. Hello. You are. Sorry, I don't know what happened. My internet crashed or something. No, there's no problems. I picked it up exactly where you were. And now you can start at the top. Okay. At the top again. All right. Sorry about that. We are like a single deployment with several boards. Yeah. All right. Thanks for for catching that thread or mark. I don't know. Okay. So the next one removal of the legacy command line arguments related to logging. Right. So there's a couple of flags which we removed. I have not listed in my notes. So I need to get them later. I don't know Mark or Fred. Maybe you can jump on this. Otherwise, I can move to the next one. I had the list, but I don't have it present right now. Yeah. Right. Okay. So if you have any questions about this, I can, I can get it in the meantime between the scenes. The next one deprecation of non-inclusive cube CTL flags. So, right. So it's part of, so we have like an initiative in Kubernetes to remove flags which are not inclusive. So we have, for example, removed now the prune right whitelist flag. And so we don't want to have like whitelist thing, blacklist things, stuff like this in flags or like in the community project. So we now replace it with the prune allow list, which has the same meaning. It's just a different name. The next one deprecations of cube CTL run command line arguments. So there's several options and arguments in cube CTL run, which are marked as deprecated. So cascading, so the flags cascading, fine name, force, grace period, customized, recursive, time out and wait. These arguments already ignored. So we don't expect like any problems for the next one. The CRI v1 alpha 2 API was removed. There might be some like problems in your classes. So some context for this. So after we removed the Docker shim in 1.25, we added in 1.24, we added in 1.25 the v1 alpha spec, v1 API spec, and deprecated the v1 alpha 2. And we now removed this v1 alpha 2 spec. And there might be like, as I said, like some implications with your CRI. So for example, if you use container D and you run a version 1.5 or another one, this will not work. If you run something else, you need to consult the documentation or like the vendor. Likely this is also like just handled by your platform provider, public cloud provider, so they upgrade it for you. If you do it like everything on your own, then you need to watch out for that. For the next one, the Glaster FS plug-in was removed and is available in three drivers. There's not much to say about that. We deprecated it last cycle. The entry open stack cloud provider is removed. So this is the Cinder volume type. There's also not too much about that. If you have any questions, drop them in the chat. Otherwise we can move on. Just a note in terms of the logging flag, it's essentially the realization of an overall of the catalog component. And just about every single flag was deprecated, only minus v and others were caps. The rationale for this is on the cap, but it's aligned with the restructuring of the log infrastructure in Kubernetes. So the functionality is there. It's just that the catalog itself will not have the flags and the information will be accessible in other ways. Awesome. Thank you. And so now we will do a per se updates in which we will pick some of the ones that we've briefly discussed before and a lot of new ones and give a one page overview of each one with links to the active to the enhancement to the cap. And in some circumstances also a link to the feature blog, we have 15 feature blogs in this release, which is quite a high number. And these feature blogs are a very good way to have a more direct knowledge of those specific features. If not, you have always the cap, which is the Kubernetes and enhancement description that is used and the and the enhancement itself. We will start with seek API machinery. And I'll pass the button again to mark or again now directly to me. Hi, everybody. We are there are a lot of enhancements and we are kind of only have an hour here so a lot of these will be pretty quick too so just give a warning once. First up is the enhancements from sake API machinery, sake API machinery is the special interest group responsible for pretty much everything related to the API is an API server here. Next slide. Yeah, I'm. Yeah. Okay. The first one is a validating admission policies this one this enhancement is going ever went alpha status. This introduced a common expression language for doing some basic validations and for your as an admission controller. This is an alternative to setting up a meat or like an admission web hook, which can be very burdensome to kind of maintain and deploy. So this is a much lighter weight option to do simple validations. Next is the aggregated API discovery feature, which is also going into alpha. This centralizes the discovery of all the supported API endpoints in your that the Kubernetes API server knows about. And there's so there's new to two new endpoints one that gives more information about each end point and one that's the kind of the aggregation of them. And using this will help reduce load on your against your API server because clients no longer need to spam the API server to see what all the available endpoints are. And last is the cube API server identity which is graduating to beta. This just gives a unique identity to each API server instance so you can identify if there's problems or things like that. Okay, next is sick apps sick apps is responsible for basically defining and how application and workloads are defined and managed in their cluster in the clusters. So first is this job tracking without lingering pods is graduating to stable so previously before this enhancement if you were scheduling batch jobs, the job controller needed to keep completed jobs around in order to maintain state, which caused the next a lot of extra kind of stress in your cluster, but now that that the job controllers been re architected no longer need that and some enhancements with this are the job controller can now scale up to like 100,000 current 100,000 concurrent pods which is much more parallel and scalable than previously. Next is this allowing for a stateful sets to set the replicas numbering to control the replica numbering. This enhancement is going to Yes. And this this is this graduated to alpha in this release and this allows for your staple sets, you can specify the where you want to start the numbering for replicas from and this is useful if you need to restart your workload or you want to work or migrate your workload, cross namespace cross cluster and and all of that. Next is this pod healthy policy for pod disruption budget. This is this has graduated to alpha. This enables specifying pod disruption budgets for pods that are not ready. And this can help prevent data loss by preventing not ready pods from being evicted. So until somebody has a chance to either automatically or automatically or manually go and recover that data. This also prevents some deadlocks in the system where you have a lot of pods that aren't ready. You can request that they do get evicted now. And the last one for sick apps is this retrieval and non retrieval pod failures for jobs, this is graduating to beta. This provides a mechanism to enable workflows to differentiate between retrieval and non retrieval failures. This can help enlighten your your cluster or things like transient or infrastructure failures to retry on those and not if it's like a workload failure. And for sick often is sickly and seeing instrumentation. I'll pass it back again to Leonard. Alright, so on my side. I don't know I have the next bug maybe I still see the validating admission policy slide. So it's kind of stuck. But I can just pull up the slides on my side and but it is I think that is everyone. Yeah, you see reduction of secret base service account. This is some bug on my side. Okay, but it doesn't matter because I have the slide as well. So I can I can just pull it up one second and okay. Right. So for this one, so we are in sick or reduction of secret base service account tokens awesome. So this cap graduates to beta to the beta stage and it introduces actions to reduce the surface area of secret base service account tokens. So the goals are no auto generation of secret base service account tokens. Standard. You can enable this and removal of unused auto generated service based account secret based service account tokens. So these are some tweaks, I would say for the next one. That's all right. I don't see when the side changes. Okay. Yeah, I will tell you when I change. Okay. Also API. Okay, we have. Okay, all the API to get self user attributes right so this graduates alpha as you can see on the right side. It adds a new API endpoint. And then you can use to run who am I, which you basically on cube CTL, which is a nice addition, I think. So this is a new API endpoint which gets added and also a new cube CTL command. So pretty neat feature. Secret CLI. Right. That's one. Or should I introduce the six. I mean, it's a sick about the CLI basically so it should be sort of the safe exploratory I guess the six CLI has one kept this cycle it's a stage beta about cube CTL events. So there's in the past, or we are still using cube CTL get events. Now there's like a new, like top level command, which is cube CTL events. So they're like some internal reasons why this is needed some limitations. So, yeah. As far as I know, there's at the moment, no, like new features, but this enables us to add like new features which the community requested to it. Okay, I've changed the sick instrumentation. Okay. So the sick instrumentation, I can just read out covers best practices for cluster observability through metrics logging events and traces across all communities components and development of relevant components such as K log and cube state metrics coordinates metrics requirements of different six for other components including finding common API's starting with the open API v3. Right. So this cap is at stage alpha and it basically updates cube CTL explain to use the open API v3 spec and no longer API v2 spec. So this just enrich the data which you get if you run this command. If there is, if there's no API v3 spec available, it will fall back to the v2 spec so there should be no issues expected on this side. Right. For the next one. Right. Right. Kubernetes component health SL eyes is a new cap graduating or it's stage alpha. It exposes new health check endpoints which should allow creating new SL eyes and then like related services and agents and so on can create new SLOs based on that. So for the next one. Extended metrics. Exactly extended metrics stability. So in which which at graduates to alpha. So this is in addition to the metrics stability framework, which we introduced a couple of cycles ago. There's also very nice blog post if you're interested about that. So this cycle we add a little bit more like two new classes to it. Internal and beta. Which is like, like, yeah, for the most part like internal internally. I don't know actually actually how like if how much does this affect like the end user. I think the metrics stability framework was very, very well received. So adding to this is a nice addition. And and you're done. I think now we're entering. Well, then for now at least. Okay. Now, we're entering sick network, which covers networking in Kubernetes and as is often the case, the network that's quite, quite a few enhancements. I will actually start by saying something that I think would be important. We've been talking about alpha beta and stable issues, just a very quick overview on what does this mean. Obviously this in enhancement starts as alpha proceeds to beta and then reach stable. If they do not reach stable after a while, they can be obviously deprecated as we showed before. And the major differences is that alpha features are this in general are off by default, but can be enabled by using a feature guide. And stable features are considering a maintained supportive within the long term part of the off of Kubernetes. And so with that, we have this enhancement of surface internal traffic policy that great great ways to stable the service internal traffic policy that gratuates to stable and which essentially allows to define a specific policy in terms of the service that will allow routing to be limited to services running on that same node. So to limit the forwarding in terms of the service and limited to the specific target. We have, and these are all relatively related that are connected enhancements. Proxy terminating end points enables zero downtime deployments for services with external traffic policy equals local, this because in some use cases and depending obviously on many different configurations choices, it was possible that when changing the external traffic policy, some downtime would happen. This enhancement reduces the death potential traffic loss from Q proxy unrolling updates, exactly because the traffic was being sent to pods that were terminating and that's unable to address that request. Tracking terminating end points graduates to stable as well. And this one adds a way to track the terminating states of an endpoint through the endpoint slice API. So not by getting the information by pod but specifically using the endpoint slice API which obviously is much more scalable and enables consumers of the API to make smarter decisions when it comes to handling terminating end points. Minimizing IP tables restore input sizes. This is a new feature, an alpha feature, which is actually quite important in terms of performance for very large clusters because the IP tables restore command can take quite a long time to run due to the sheer amount of network rules that end up being created by the several Kubernetes networking objects and policies. So this enhancement drastically improves the performance of the IP tables restore command. Support of mixed protocols and services which type load balancer. So this is a enhancement that graduates to stable and it enables the creation of a load balance service that has different port definitions with different protocols allowing users to expose their applications through a single IP address but different layer for the protocols with a cloud provider load balancer. This for example means that there were some cases where this was already possible through TCP or UDP, but this one generalizes it and reduces the coordinate cases that were not really well documented that could result in this not working. This adds that support explicitly and does makes it both possible and also consistent and resilient and defines that expected behavior. Reserve service IP ranges for dynamic and static IP allocation graduates to stable. So this is essentially around this. Plus IPs can be assigned dynamically or statically with this enhancement does is it splits the range that is used by static and dynamic allocation. So that's a specific situation can be avoided which is someone specifying a static IP because it was free at the time but by the time it gets used, dynamic allocation would already have used it because it was free in the meantime. So by splitting between these two uses, it's clear that part of that range will be manually consumed and the other will be dynamically. Expanded DNS configuration allows Kubernetes to have an expanded DNS configuration that allows more DNS search pots and a longer list of DNS search paths. This graduates to beta. And essentially is adding to Kubernetes the evolution that have been done but only in terms of the DNS supports in the new Lipsy and other underlying Linux components that adds more configuration options and remove some of the limitations that existed at a certain point in time but do not make sense to keep right now. And with that, we end the list of enhancements from SIG network and we have the enhancements for SIG nodes. And if I'm not mistaken, this is picked up by Mark, right? Yep. Yep. Thank you, Fred. So SIG node is they are responsible for all of the components that run on the nodes and well, that control the interactions between the pods and the hosts most notably the KubeLit. Okay. So this enhancement dynamic resource allocation which is graduated to alpha. This adds a new set of APIs that allows for workloads to specify resources other than memory or CPU. And it also allows for sharing of resources between multiple containers or pods. This is quite a big enhancements over the previous way of allocating resources so anybody who's interested, I'd recommend them to go read the blog post and read up on the cup. Device manager, device manager is graduating to stable. This enhancements has actually been in beta since 110 and there was just finally time to graduate it. The device manager is kind of a plug in and I think it's an API. It's a way of kind of advertising and allocating different external devices which you can use and assign into your containers such as like GPU devices and FPGA devices. Next is CPU manager which has also been in beta since 110 and is graduating to stable. On the CPU managers, it's part of the KubeLit and it's responsible for assigning the CPUs to containers. And prior to this, there was potentially a lot of issues. If you specified more than one CPU for your resource limits or requests, you could land that could get split across multiple CPUs and you would spend a lot of time just cycling with that. And next is the KubeLit credential provider. This is graduated to stable. This provides a plug-in model for registering and basically for offering two different container registries. So previously, every time the KubeLit wanted to authenticate to a new container registry, it needed code needed to be added to the KubeLit to understand how to talk with that. The KubeLit credential provider provides a plug-in model to eliminate that, which is supplying maintenance and making it easier to support more registries. Next is this improved multi-numa alignment the topology manager. This enhancement is graduated to alpha. Previously, the topology manager, you could assign pods to specific numa nodes or ensure that all of your containers land on a specific numa node, but it didn't have any kind of awareness of the distance between the numa nodes, which is becoming more of an issue with multi-socket processors. So this enhancement allows you to basically specify like a minimum distance or between your numa nodes to get these workloads to kind of land in the same proximity of each other. Next is this KubeLit-evented PLag for better performance or the POP Lifecycle Event Generator. This enhancement is graduating to alpha and this enhancement is tracking outlining changes to the KubeLit and the container runtime interface to move to a list watch model instead of a continuous polling model. And the goals of this is to reduce the steady-state CPU usage of the KubeLit and the container runtime. But last I think is the CAdvisorless CRI full container and pod stats enhancement, and this has graduated to alpha. This allows for the KubeLit to get all of the container and pod stats over the CRI or the container runtime interface from the container runtime instead of also having the KubeLit query into the CAdvisor to get some missing stats. So this is just kind of removing some duplicated work and putting more responsibility onto the container runtime which is where it belongs, thank you. All right, back to my slides. So for SICK release, which handles all the releases. So for example, the release team is part of the SICK release. We have one cap, Signing Release Artifacts, which graduates to beta. So this release or with this cap, we now sign all the release artifacts. So users can verify the integrity and of the downloaded resources. So this includes all the like binary artifacts. So what we listed here, so the tar balls, the binary artifacts the software bill of materials, the S-bombs and we use cosine, yeah. So there's also, for example, if you're interested in this entire like S-bombs theme and topic and everything, the Q&A release team is quite like a forerunner or like a pioneer, I would say a little bit. So if you're interested in this, there's also a lot of good resources, blog posts about this topics. All right, to the next one, SICK Scheduling, which is responsible for the components that make pot placement decisions. We have two caps. The first one is pot scheduling readiness. So currently, pots are considered like ready for scheduling as soon as they are created. And in general, this is fine, but in some scenarios or like often or in few cases, this is not the case and pots are not ready as soon as they are created. And at the moment, or there have not been like any options to control that behavior that these pots are not ready. So with this cap, we introduce a new parameter to the API spec, which allows you to control this behavior. So you can set scheduling gates, which defines if a pot is, for example, unschedulable or you can define like a pot scheduled condition. For the next one, take tains, tolerations into consideration when calculating pot topology spread skew, it graduates to beta. So this defines a node inclusion policy and topology spread constraints, which you can set to control the behavior where the pots are scheduled. So I will pick back to describe several enhancements of six storage, which is responsible for ensuring that different types of file and block storage are available wherever a container is scheduled. So it tackles everything storage related with quantities and trying to speed things up a bit. I'll go through this relatively briefly. Non-grateful node shutdown, this is a beta feature that allows stateful workloads to fail over to a different node. After the original node is shut down or is in a non-recoverable state such as hardware failure or the broken OS. Allow Kubernetes to supply pods FS group to the CSI driver on mount, graduates to stable. This essentially allows the CSI driver to have the option to apply the FS group setting during volume mount point in contrast with what was before that was defined in one place and was not setable by the CSI driver. Provisioning volumes from cross-namespace snapshots. This is an alpha feature that allows it to specify the data source for a persistent volume claim even when the source data belongs to a different namespace. With this new feature enable specifying the data source rep-filled, you specify data source rep-filled and once that Kubernetes checks that access is okay, the new persistent volume can calculate this data from the storage source specified in that separate namespace. Retroactive default storage class assignments graduates to beta with this enhancement. There's no need to create a default storage class and only after that the PVC to assign to that class and also allows that any PVC without the storage class can be retroactively updated to specify to that storage class even if the PVC is recreated before that storage class was defined. This fear entry to CSI driver migration part of the overall movement of migrating from removing things from the entry Kubernetes source to external drivers. This one graduates to stable and migrates the internals of the Vista plugin to the Vista CSI driver while maintaining the original API and exactly the same is done for the Azure file also graduates to stable also with the same motivation and the overall same approach as the one before. And with this, SIG Windows that Mark will cover. So SIG Windows is a kind of a horizontal SIG focused on supporting Windows functionality across all of the different components like networking, storage and node. So this enhancement for support for Windows privileged containers has graduated to stable. Support for privileged containers on Windows were kind of allow the containers to access host resources and are very useful for many operational type workloads. And so now they have access to all of the host resources and this enables running things like your CNI solutions, node exporter, node problem detector on all that and managing them as demon sets. And next is a host network support for Windows pods. This is graduated to alpha. This adds support for the cubelets who request that pods getting scheduled on Windows nodes get added to the host's network namespace. This is one kind of a parody feature with Linux but it also helps issues with a port exhaustion for large clusters. And this ends our SIG updates. And I think we are actually on time just some final words around the release team shadow program and QCon. So the release team shadow program is a Kubernetes release team apprenticeship model program that in each release, it recruits a certain member of apprentices that gets involved in each specific release team. There are several different release teams enhancements, signal, comms, docs, release notes, et cetera. And these teams take on this shadow shadows in order for them to have hands-on experience with developing a release. And they participate in the release cycle and hopefully they with this get involved not only in other Kubernetes community efforts but can also potentially lead the teams in the future. And this is the program. There are several different teams as I mentioned, release team leads, enhancements, CI signal, but triage, doc, release notes and communication. Each team has one lead that selects between three and five shadows and each release takes four months. What I can say right now is that 127 is already ongoing. So the shadow program is not accepting people for the 127 release right now, but anyone listening, please pay extra attention after the 127 release is published because in the following weeks, an update is sent to the Kubernetes mailing lists that shares a form in which anyone can volunteer and hopefully be integrated into one team and experience being a part of a Kubernetes release team. A final word about the Kubernetes 1.26 at KubeCon Europe. As I mentioned, KubeCon Europe will happen in Amsterdam in the 17th of April, well, it starts in the 17th with the contributor come and then 18th KubeCon Europe. Several of the release team members will be there. So we will be more than happy to share some additional thoughts and ideas with anyone attending. We share here some transparency reports for both KubeCon Europe and North America, but suffice it to say that is one of the biggest Kubernetes and cloud native related meetings. So we do either physically or virtually, we would like to be able to see any of you there. And as I mentioned, share some thoughts, discuss Kubernetes present and future or just any other topic. And with that, we're done. We still have five minutes and we are more than open for any comments and questions. Thanks everyone. All right, let's see if we've got any questions or a little chat, about five minutes left. So ask those burning questions now. Have y'all maybe where they can reach you if you think of something after we end? I think that perhaps the Kubernetes Slack would be a good place. So let me... Okay. So in the community Slack, we have a channel for each SICK, SICK Release and all the other SICKs. So if you want to reach the SICK in general, you can, this would be the best place to go. If you have something very specific, maybe about internal processes, I don't think there will be some questions about this, but there are also other channels which are more about those. So for example, if you have questions about the enhancements team, there's like a Release Enhancements channel as well. And you can also obviously find us or anybody else from the team and send a direct message if you don't want to ask publicly. This is totally fine too. I just shared the Kubernetes Slack address in the chats. And obviously, I think all of our names are easily findable on Google. And so feel free obviously to... And actually reach us in Slack there individually if needed. Perfect. And yes, if Fred, if somebody will send me the slide deck that you used, I will upload that to the website as well. So you'll be able to get both the recording and the slides. So yes, Victor, you can. All right. I don't see any more questions coming through. So we will wrap this up, but thank you so much Release Team. Y'all are wonderful. And thank you everyone for joining us today. We will have this online by this afternoon. So if anyone missed it, it will be ready to go. And everyone have a great day or evening or depending on where you're calling from. Thank you. Thank you all. Yeah, thank you everybody. Bye-bye. Cheers.


Hey what's good y'all it's your boy Don from the Don showing friends and we're back for another kpop reaction today We're doing Lisa and the bro Carter's back in the building. Yes, and I Do not have a catchphrase, but it's all good because once again, I am happy to be here Man had a long day been working, but they are doing the food truck Thing in my area that I live in out here and there is a lobster food truck So I already pre ordered it. So after I get done here I'm gonna go pick up a lobster roll and some lobster tacos. I ain't had some lobster tacos. Oh, I never had that So I'm excited though. I want to watch another performance video music video Of my boy Don here. So yes, sir. Yes, sir Oh, I have no mistakes. I'm a vegetarian Excitement not me. No. Yeah must be nice. No comment. So, um So today, yeah, we're doing Lisa money exclusive performance videos So if y'all enjoyed this, please let us know and if you have a request for a video We'll really help us so much is you put the links in the comments Um and let us know if the video glitches. We're trying to work on why it keeps Uploading like that, but we're working on it. So thank y'all for saying something. Appreciate the feedback. Also. Yes Thank you. Yeah. So hit the like button. Make sure you subscribe ring that bell Make sure you share it and uh, yeah, let's keep moving forward. So let's go ahead and get started on this one Uh, let me turn this up real quick. All right in three, two, one Right off the bat How big is that? Why it had to be? Right off the bat Let's go. I wonder what they're going to do with this choreography with Yeah already So what we talked about the last video that we did we did the bts Is making sure that that the choreography in the video is put together now these shots right here I keep wondering what y'all these are not my favorite shots when it comes to dancing. It's because as a choreographer I'm I'm trying to see like the legs and everything But you have to make a sacrifice and they chose the arms and I know they're gonna move back and forth But this is the one shot that I'd be like But I understand it like I had to I learned and I do love it sometimes. So yeah But I will say though one thing I do like What I like remember when I talked about the leading lines, right? Leading lines I went and looked it up. I did some google So the point of leading lines and videography and photography Is it's supposed to direct your attention to what you want the audience to focus on So right off the bat you see them in the middle of the frame If you look look at the leading lines look at the the lines on the street Look at the lights behind them and then even look at that. So that's really Like I said every Background everything that's part of the videos all on purpose. Yeah, but the leading lines and then look boom Because they want you to focus on her. Yep and so now So they just keep that some extra symmetry right there. Yeah I first saw them outfits are cold. I love the outfit Yeah, and all the cuts are on the beat. Yeah See the bottom. Yep To cut. Yeah, cut. Hey, yeah, I like that. Like I really did like that. Nice. Yeah. Yeah. Yeah So You saw how change change and then it cut cut out. So we close in we close in cut Now we back it up now they coming in now they stopped we going in Back up So how you saw the song she did that with her hand. We backed up and what she turned you say how she turned to the right Camera boom was ready and that was a real nice transition. It was a it was a hard jump cut, but it wasn't the next scene Yeah, so Yeah Different I actually never seen. Well, I have like the background yet. Yeah. Oh, okay Boom, okay Let's go hold on I gotta uh, I gotta hold on. Let's let's Oh, this this is cool shot. Yeah This is a cool shot Boom cut cut cut cut cut So they see where our arms drop So there's a part Because I had to get into that that dance mode real quick There's a part where she kind of like dropped her hands and the camera went down Like if you look at it carefully like they dropped it down, let's go on the mute for a second Well, look check it out though. Check it out. We're before you get into that We want they obviously Lisa. Yeah, this is my first time even hearing her seeing her. Okay. Okay, but The goal of this is she's the star obviously So look at the leading and the lines don't always have to just be lines Like it could be people what's behind her. So look one two one two three, but still it's all Supposed to just like they're in the back. So you see them, but it's supposed to focus your attention It still has a good balance. Even look it's it's all balanced. It's all balanced Maybe as all things should be shout out to Thanos. Well, that's a great philosopher right there. Oh god Okay, right here. Look at this Come in room. They dancing dancing Oh, no, I muted it. I muted it so they can see this part. Don't start it about So you get right here Boom, she's about to drop it. Wow. Now we're here and she bumps She bounces up like a jump. She jumps up with it and then she goes right back Black and and for me as a dancer, I'm looking at okay. That's what y'all want us to focus at So that means there's nothing really important about the legs. It's just the upper body movements That's happening and as you can see she got a hand gesture, which we call that a crumb is styling hands and illusions and so that I'm sure that's a that's a definitely a director director choice because Our job as videographers or cinematographers when we're filming dance is to make The dancer look as good as possible. Yeah, so I don't I don't know if uh, you and so you you will find Um videographers that are in that that shoot dance Also have some dance background And so they kind of know like you can look at a dancer. Okay. Well, they do his strong points are really with his arms I don't know dance like that. But the strong points are his arms. Oh, he really has some good footwork So the so when you look at whatever a dancer strengths are or if you're working with an artist I imagine who's not really a dancer, right? But you want to make them look as good as possible You got to focus on what's going to make them look the best. So That's why that's why I'm getting it now. Why okay, that's why we're focusing mostly on You know upper body within what she does some other dances. We do a wide shot Yeah, because you don't want to miss the the good part And that's basically what it is is that you don't want to miss the uh, you don't want to miss that good part of the movement Yeah Let's go The lighting is definitely different. That's a good shot. Hey, was she killing it though? Oh, yeah Let's go She killed it. Yeah, very everything is mostly close up. Yeah a lot of it That's style. Yeah I'm gonna do my mother dance. I'm gonna do my mother dance. Okay, Lisa The style like the style of the camera shooting the dance and it's really close up And and and it's like the choreographer definitely had to make sure that everybody was really moving because That's what they decided not saying like they don't have other shots Where it's showing whole body, but it's so interesting that I'm seeing like it's so zoomed up So that's why I'm not reacting like oh Because I actually I did watch the dance practice already. So I know the choreography But this is where there's a choreography. How you feel about the choreography the choreography is cold That's why I'm quiet because I'm like man the dance practice was like, you know, I'm being a dancer. I'm like We missing some shots. I have to remember too, right? So this is not the music video. This is a performance video Yeah, so the performance video. Yeah, that's from what you've seen. What is the Or maybe I couldn't explain it to what is the what is the point or what's the difference? Or what are the you know for a music video and what's the purpose or what are the they are trying to Simply but it is it's showing how visually based and this is opinion out of fact Is from my perspective when you get the dance practice, you see the dance practice You see everything but the performance video is putting that real visual out there. How it's looking So more stuff is zoomed up. So if a dancer is watching this like dang, I know that Choreography, it's like yo, make sure you remember this is the performance video So they're getting all these different shots and the music videos where they really go in a bag And then the music video is like we in the bag Okay, colors and all that but I just think it's still incredible that I love that they have like three different I was initially judging this and looking at it like it was a music video because I mean you look at This way this would to me. This would be a cool music video This would be a cool music video so So but is the regular is the is the music video for this song out yet? Or is just a performance video not gonna lie. I don't know but I know the fans Okay, so if it is out there, please send that one. Yeah Because this choreography is cold and I know y'all saw the dance practice the choreography like that That's that's what I'm saying. I know the choreo. So I'm trying to Look, I'm telling you this choreography is cold. I've seen this Okay, so they do the Yeah, because this is Yeah, this is a music video. This is like a performance video, but like the choreography is cold She got a new fan.  Yeah, I like who said Yeah, I like I like her. Yeah, Lisa gets it in Yeah, like she she definitely gets it in. Yeah, man. I I love I love her. That's what I'm trying to remember I'm like, this is not the dance practice down because I know this choreo this choreo is cold See this choreo is cold I mean It just that's just where I wanted to land. This is wanting to stop there. I like that Yeah Yeah, that's why I was so thirsty that let's see all of it I'm talking about thirsty because the dance practice is crazy That's what I'm trying to remember. Like, hey, yo, this is not the just not the dance practice because They was getting in in the dance practice That was a whole whacking drop it on you. Yeah, like eat. All right, Lisa. Yeah, I'm gonna have to I'm gonna have to Listen to some more of her music. Oh, yeah, she's yeah She like that's why I'm trying to it's like watching the video. You like remember this is the performance video Remember this performance video remember this performance video because the dancer me like yo The dance practice is crazy and I really I believe I know I saw the dance practice You know what's so crazy like I So she so she's speaking um english Yeah, so I didn't I need I would need to watch this again because I actually want to Like listen why let's read the lyrics and what she's saying But so far from overall man song song hype song type. I like the different breakdowns that it had Um, she definitely got got flow. Definitely got flow. So Cool. I definitely hear the influences too. Yeah, definitely hear the influences, but um I like it. Shout out to Lisa. Shout out to y'all too. I really like this Oh, yeah, but listen y'all if y'all join us doing, you know, this artist right here Please let us know put more in the comments. Um, we have more in a way Thank y'all for the request of what um, which I want to watch So we're gonna try to make sure that we get those done and thank you for letting us know that the video was glitching We're really trying to solve that issue right now. So I'm gonna go ahead and edit this video Then hopefully this is not glitching if it is so sorry, but we'll see y'all soon Please


Everybody forced here up in 2022 NT collegiate football hobby four box case number five Random divisions take a look at the results right here. There's a Lincoln chat that'll take you to the site You can always find them there as well. Thanks for joining everybody. Here we go Last break daytime then a Sam's gonna get set up. He's be live in a down hour and 15 here. Here we go He's got baseball basketball and football break spots for tonight. Personals will resume after group breaks tonight These are only 550 basically guys for a per personals of this personal boxes Last break daytime, let's make it a good one 13 a 99 Najee Harris on the base parallel AFC North a Citrus Bull patch auto 5 of 10 Tyler Goodson NFC North Packers NFC North right there Nice card there. We've got a what is that? Patch auto 7 to 25 Tyler McBride or Trey McBride see me Trey McBride NFC West What is that from is it just like Colorado State the TE they wear blue unis at any point Could be all state too. I don't know Colorado State fans or college football fans help us out Jumbo Jersey Auto Kyron Williams 67 to 99 NFC West dual Jersey Drake London NFC South 9 of 25 That's pretty three color colossal patch Kenny pick it nine out of ten Go AFC North nice three color pit panther patch Silhouette signatures Brian Robinson jr. NFC East 35 out of 99 and nice AFC North just crushing it all day today Silhouette signatures George Pickens 91 of 99 sweet Pickens Here we go AFC North get that in a mag for you. They should start calling Pickens and pick at the pick to They're not a thing anymore that is a Roger Stovak Navy Roger Stovak 18 of 39 NFC East Oh, stay pregnant from that's pretty cool. Yeah, the Colorado. I've seen I think I've seen those now that you say that Those are pretty cool. Oh, look at him. We're almost out of here dual Jersey Kenneth Walker the third three of 25 NFC West Peer strong junior rookie auto AFC East 62 of 75 Sameer white 20 of 25 Rookie patch auto book for the AFC West Raiders AFC West George all over this stuff. No Kobe Dean team logo signatures 14 of 49 NFC East Jared stittum hold all the sit-ins now Jersey Auto 94 of 99 Going to the AFC West Raiders AFC West pick it 88 of 99 Rookie Jersey Auto book AFC North can't not pull a picket guys Can't not do it There you go AFC North Congrats on that one and a Christian Watson Jersey Auto 73 of 75 NFC North. I realized Christian Watson has the same colors in college and in the pros We must have this is this is reddit pick it all day. Sam. I might not pull one picket tonight. I don't know We haven't seen a ton of Willis though, and we've seen a reader here and there Corral here and there Haven't seen any Bailey's app easy on a checklist like He might not be in this it's possible He's all over IMAC though 3375 that press got NFC East Diesel Jersey Auto K Von Dibbado 10 of 99 NFC East Jersey Auto DeAndre Swift NFC North 52 of 75. Oh, that's nice Jalen Hertz 20 of 39 of the Jersey Auto NFC East the Sooners Jalen Hertz Take that Bama either way Congrats Kirk P on the Hertz MVP can send her this year Only undefeated quarterback Rush, sorry Undefeated Triple Jersey Kyler Hertz and Baker the the OUQB is there Kyler NFC West Hertz NFC East Baker NFC South random at the end Dual Jersey Olava and Wilson to Ohio State receivers there to 99 NFC South and AFC East crazy They went like back-to-back in the draft pretty much. They're both really good A lot of good receivers this year Oh, that's sick Cool logo cool hit for the NFC South Desmond Ritter team logo signatures 10 of 25 Nice hit on the Ritter right back that one Bearcats Jersey Auto AFC South Traylon Burke 67 of 99 Nice Berks Sounds like a nickname for like Birkenstocks or something. I got my Berks on Even some of the flip-flop brands are crazy Have to check it out when I get home Go on there see what deals are left. Yeah, Jonathan Taylor 24 of 75 for the AFC South Breaker injury workers comp coming Jersey Auto sauce gardener 37 and 99 AFC East Isaiah Spiller RPA 17 to 25 AFC West. Yeah AFC West on the Spiller Jack Cone RPA. He was only a cult 89 to 99 AFC South Alec Pierce patch card AFC South 10 to 25 That's a big patch Jumbo patch Marcus Mariota NFC South to a five three colored organ patch Player worn Mariota a five at NFC South You've got a Sam Howell patch auto six of 39 NFC East The first howl ought to be fooled We didn't give any other quarterbacks any love it's been all picket. It's been him instead of them all day and On the back of course George Pickens team logo signature 17 to 25 AFC North Kenzie is not gonna want to break with me again. You go AFC North. Congrats on that Let's do these two randoms and a recap Okay, two randoms here Dual Ohio State receivers a la va for the NFC South and Garrett Wilson AFC East And then triple Bama or triple OU OU QB's here Kyler NFC West Hertz NFC East Baker NFC South to 99. Good luck a 6 and 4 10 times Good luck one first up top gets the cards by the way two three four five six seven eight Nine and ten it's gonna go AFC East on the Wilson and a la va another ten times for the OU QB's here one two three four five six seven eight nine and ten NFC East The books we had an AFC West a mere white book the 25 RPA book Kenny pick it to 99. Congrats to the AFC North No crazy patch on 99 Blue patches there Relics we had Kenneth Walker the third NFC West Drake London NFC South Marcus Mario to NFC South to a five Alec Pierce AFC South to 25 Kenny pick it AFC North to 10 Otto's now pierced strong AFC East to 75 Nicobi Dean NFC East team logo signatures Sam Howe patch auto NFC East to 39 AFC West Isaiah Spiller RPA to 25 Jack Cone AFC South RPA to 95 AFC East Sus Gardner Jersey out of the 99 AFC South Trail and Berks Jersey out of the 99 NFC North the Andre Swift is 75 cave on Thibodeaux NFC East and 99 We had Christian Watson is 75 Jersey out of NFC North AFC West Jared Siddham to 99 NFC East Brian Robinson Jr. to 99 NFC West Cameron Williams to 99 NFC West Trey McBride patch out of the 25 RPA citrus bowl patch 5 of 10 Tyler Goodton NFC North They pick into 25 AFC North team logo signatures NFC South Desmond Ritter team logo signatures to 25 NFC Salem Hurts 20 39 on the Jersey Auto and A pick in Jersey Auto to 99 AFC North. They have rushed it now. I'll do it. Thanks everybody


Troops of 82 Division Nigerian Army Inugu have arrested Godwin Nnamdi, a leader of the prescribed indigenous people of Biafra, and the Eastern Security Network Director. Army Public Relations Brigadier General O'Neill Mangwachiku said the troops of Operation Golden Dawn arrested Nnamdi on Christmas Day. Nwachiku said that Nnamdi, a notorious leader of I-POP and ESN, was arrested during a clearance operation in Incarno East local government area of Inugu state. He said that troops recovered one AK-47 rifle, one magazine containing 21 rounds of 7.62 mm special bullets and one telephone handset from Nnamdi.


It's Hopalong Cassidy With action and suspense out of the Old West comes the most famous hero of them all Hopalong Cassidy starring William Boyd The ring of the Silver Spurs heralds the most amazing man ever to ride the prairies of the early West Hopalong Cassidy This famous hero thrills his 60 million fans with action and dangerous adventure In the role of Hopalong Cassidy is the popular star of the motion picture series William Boyd and Appearing as that laughable old character, California is Andy Clyde now to our story Red Rock Mesa Shimmering in the heat of a noon sun lay mescalosa plain Stretching as far as the eye can see The squat settlement of mescalosa in the center with the pine covered hills of the Indian reservation to the right and Far in the distance beyond the white sands of the desert the flat top table land called Red Rock Mesa Gosh coffee ain't better sight. Yeah, it looks mighty hot down there She was mighty hot the last time I seen her in more ways than one. When was that California? In 73 the year before the command she wore mean another fella Know what was his name? Oh, it doesn't matter. No, it was not memory.  I'd never come back Well, I don't think we need to worry about the command she's now California. They've been behaving themselves for quite a while Well, I still ain't in love with a miss Caloosa country wouldn't be here now if it wasn't for this horse business of yours They haven't come in see Indians is about as tough as they come why I remember the time once when I What's the matter? That's funny, huh? Let's smoke over there at the side of the rid What are you reckon? I don't know. Let's take a look I Don't know looks like somebody's ranch house get burned down Still smoldering Couldn't have happened more than a few hours ago some time of the early morning Huffy, I ain't want to jump to conclusions, but there go on. What is it? Well a few years back We never had to think very hard when we run on to a burned ranch house command she's yeah We better get out of here. I want to talk to the marshal in mescalosa Get down down. What was that look in that timber there. It's a narrow. Let's get out of here, Huffy Keep down. We might get out the back. Let's go Hold it. They thought of that too. Well, they'll have to come and get me.  It won't be by shooting there. Ain't nothing else to do Hoppy, maybe not what we got to try. This is one spot. We're gonna have to talk our way out of Red rock mesa for five eternal minutes hoppy in california crouch in the blackened ruins of the ranch house Waiting for something to happen then Look where there's one. I'm coming around that bowler. Give me your hand. It's a white used to be here Good put it on the stick here There now who never thought I'd see the day when hop on Cassidy would wave a white flag as an engine You want to keep your coupé in place?  Hello over there He's coming out. All right now cover me while I go out the medium, right hoppy and don't pull that trigger unless you have to Understand. Yeah. Yeah. Good luck hoppy.  I'd rather leave him where he is. They said bring other man here. What do you want? guns You have guns.  Who are you? My name is Cassidy. Where are you from the bar 20 ranch quite a way north of here My friend and I just got here a few minutes ago pulled up on the ridge over there and saw the smoke came over take a look What are you doing in make close the county just come down here to buy some horses? I see Chief These aren't the men. You must let them go in peace Bring your friend out here, Mr. Cassidy. All right miss California here coffee That white gal doing here. I don't know if you sure came at the right time. Come on This is my partner California Carlson. Howdy, ma'am. How do you do? This is chief broken length of the command chief He's sorry. He made the mistake Where do you like what he was on you if you want you to go in peace? Mind if I ask what this is all about miss.  What do you mean? Almost every ranch bordering the Indian Reservation has been raided during the last few weeks Cattle runoff buildings burn This is one of them right here. I see Do you mind if we oh, of course Chief we'd like to talk you'd better get back to the others You tell white man our story miss I will it is well Now what makes you think these raids aren't the work of the command chief. I also know I live with them Uh-uh, I keep an Indian school on the reservation From the trouble started I refused to leave with the others I know the command chief are innocent, but it's useless to plead with the ranchers and make colossus They're ready to fight now Our only hope is to catch whoever's behind these raids so when they saw California me fooling around this ranch out here They thought they did you lucky you weren't killed. Thanks to you miss, uh, Brits Martha Brits You better be on your way now the two-hour ride to make it closer just like that, huh? What do you mean?  Well, you're gonna get our help. What do you want to do? Here's your intern Thanks, thanks very much. I Would like you to do something for me and what's that the marshall and they school of it. His name is Bob Nolan Keep an eye on him for me. Will you sure? I want to look things over in town this afternoon. I'll be back here tonight Will you meet me? All right? I'll be here You know what she was talking about happy this town sure spoiling for a fight. Yeah, she wouldn't have a chance talking to these birds Well, let's see what our friend Bob Nolan thinks We're getting together tonight to take some action on this thing. I hope you'll be with it But if you ain't we're gonna go it alone. You're not gonna do anything till I say so Whitman I tell you we're tired of waiting three ranches burn in the last two weeks over a thousand head of cattle Them red skid and vomit runoff, but I'm not setting off another command she warned you I've got something more than suspicion to go on. Is that the only reason Nolan? What do you mean are you afraid your young school mom might get hurt if we tackle her precious Comanche Think it over Nolan Okay, what do you want? I'm hop along Cassidy. This is California Carlson. Howdy Marshall. Howdy We talked to miss Brit up in the foothills this afternoon. Martha. How is she fine? What did you say about she's gonna see it through from the Comanche side? I was afraid of that. Yeah, who's that folly you were talking to? Sully Whitman lost 500 head last night Whitman. I look shorter familiar It's like all the rest of them now ready to shoot a command she on site. How many counter missing now at least a couple of thousand There's no ranch around here hasn't been hit at least once. Hmm can't run all 500 had a cattle without leaving a trail We followed cattle trails till we're dizzy got nowhere. What do you mean? You got nowhere Bob? Every trail leads to the same place somewhere in the edge of the Tierra Tierra the Tierra de la Muerte Sam desert Sean what happened ambush at the edge of the Tierra. They got Bill and Larry You got horses handy Cassidy right outside, okay, come on with me It'll be dark when we get there, but I'll show you what I mean Where's the fire from Sean the rise over yonder you can see it in the moonlight back Well, what do you make of it Cassidy just like the others? Cattle tracks leading right out into the desert. How far does the visit go hundred miles or more nothing but sand dunes? Wind washes out the tracks five minutes after they're made. Hmm. Those cattle got to be somewhere You can't make a couple of thousand they'd disappear. You say you couldn't see you fired on your Sean. Nope The shots came from that rise over there Look there in the moonlight. It's an engine get down There he goes. Come on now. Here's where you fired from Sean. Yeah, no use trailing them now He's halfway through the desert and I'm satisfied now. Yeah, I saw him and it was an Indian It's all I need only one thing. What's that? Take a look at these tracks here First time I ever heard of an Indian riding a horse with iron shoes Might have stolen the horse.  I know you are too Baker at the edge of the desert this afternoon I'm concerned that's the last straw. I'm ready to move away. I'm gonna go struck against the Comanche Nation I'll start it up all over again I know there isn't a card in the lot here. I'm the last one is gonna run out on my duty here Hop along Cassidy and I were down to the scene of the shooting tonight And we still aren't satisfied. It was done by the Comanche. I look boys. Oh, I'm asking you wait a minute I'd like to ask the marshal here one question. I'd like to Because he's afraid a certain little school mom might get hurt in the fight All right boys, I'll get there There's only one way I can answer that kind of a charge Be saddled and ready by dawn. Oh, we're waiting to hear that Coffee in California ride up to the ruins of the farmhouse where they first met Martha Brick Hold it We'll see in a minute. There she is. Come on Martha We've been waiting for hours. They kept us pretty busy. Who's with you broken land good the town's up an arm Oh taken off a dawn arms of the teeth. I was afraid of that I'm Bob's forced into it. He asked me to get you out of here. The Indians are depending on me I can't deserve them now. Don't be silly. You can't help them by hanging around either But where can I go? Can't go back to make galosas.  What is it California? I'm thinking we haven't got time for that No, I'm thinking the time the command she's run me and that other fellow Fred Rock Mesa Why can't we take miss breath there? There's a trail no one knows about on the far side this fellow showed it to me. His name was What's the matter? I got it. The fellow was up there with I remember who he is. Oh, what's all of them? Solid Whitman. They're the same color that skunk who's firing up the mob down below is the fellow I got run up the mesa with you sure sure positive wait a minute now This is here in the bed Yeah, yeah, what look out in the valley there. You can see the mason the moonlight Suppose those cattle were run out into the sand dune so the wind could cover their tracks Then suppose they were turned south to the Mesa. What's it like on top prettiest land? You ever saw water there plenty of grass enough for 2,000 head of cattle for a short spell sure So Whitman pulls off the raids makes it look like the Comanches and fires up the town for another Indian war I think I know why now it begins to make sense wait or she held you left me behind Martha tell the chief to get his men together and hold up in the wood here We'll try to make it back before dawn where we're going to the top of a red rock Mesa I'm gonna leave the horses here right coffee But you see how a trailer is wider this could be so well-hidden old buckler trailer, right? wait Listen, yeah, I think we've solved the mystery of the disordering cows California. Come on now Take it easy. I might have a sentry at the top of the trail All right now around the other side of this boulder. We ought to get a look at the top of the Mesa. Watch where you stand Hoppy look right below A couple more on the other side there must be 20 men here anyway, and we only want one of them first Bring back with us for a souvenir Somehow we got to get one of those guys away from that nearest campfire You're giving me the willies facing around like that. I'm called. You mean you're yellow Sure, I'm scared. Oh, yo only admitted It's crazy. That's what it is cooking up in the need and ward to keep every man in the county busy Why have we moved 2,500 here to cows off this table top? One of the horses must have walked down the trailer, please. I'll go. Yes. There we are. I'll get him.  Not a sound understander. I'll blow you off the top of this Mesa, California. Yeah, I think they're gagging his mouth His hands To hoppy no, he's got a long right ahead of him. He can make him do it side saddle Oh Drums up this expedition You're right up in front with the rest of us when the shooting starts Still sticking up for the command. She's are you Bob sticking up for you ranches if you only knew it What is it Sean? Well, it's getting light enough to see the hills now Take a look over there on the east bridge.  What do you reckon it is Michael?  I don't know who the bosses. I never saw don't tell us that pretty you better tell us the truth I am telling you the truth.  Yeah, no command she customs of California. You take care of our guests I'm going over the help with the preparations Great preparation What's he mean?  Yeah back in 73. We used to call it command she conversation Nothing like good warm peace to make a man real talk Ever had dealings with the command she's missing No You've got a lot to learn Real practical folks the command she's the chief out there broken Lance He's a command she of the old school. Don't make anything this light broken lance no more What do you mean? Well, I'm mind the time in 73 just for Adobe walls when old broken lance here had a couple of white Prisoners who knew something they wasn't telling the first one was real stubborn. He wasn't talking.  Oh, I took shot of the bitch Follower still wouldn't talk so they finally lost pinching What about the other one well, but then then command she's was awful man So when it comes other fellas turn they decided to get tough with him What you point up there it's the chief all right and the clearing by the burn cabin. I got a fire there anyone else I'm not sure Whitman couldn't see no one of course.  That's just what you might be doing Sean yeah right back to the rest tell them to stay right where they are and hold their fire until they hear shots in the clearing understand What are you doing Nolan? We're going ahead to talk to broken lance Whitman. You're crazy. What's the matter Whitman you yellow? No, I'm not yellow. Let's go. There's a cabin down there Something wrong that fire burning no one around put on and take a look if we better get the others take it easy Whitman War hasn't even started you ready to jump out of your britches.  Where's Martha? She's all right. We got to get her out of here. Why those middle never mind that now I think we got the answer what they're looking for what's that Cassidy? You will find out Whitman. Let's go Over here.  Mr. Whitman. No, just Oh, what's the matter for us? Don't you recognize your number one hand? I never saw this man in my life No, you Whitman may found the cattle in the Mesa. I've told him the whole story Why are you freezing for an empty holster Whitman? I got your gun What is it Cassidy? You can head off your army and tell them they changed their course for Red Rock Mason or hurry They'll get their cattle back Whitman and his gang have a whole 2,500 heads for out up on top ready to move tonight Well, maybe we'd better all right out there while Mr. Whitman tells them himself Yes, I want you to know how much I appreciate what you've done I think we'll hold on to it and I'm moving on to you honey right here next to Loser All through Sharon Martha with the Comanches Bob, right? I'm sure they can get along without me now and I expect you to can get along without a couple of bar 20 cow Pokes who ought to be heading back for their own rain I've been waiting for you to make that suggestion coffee get an impatient California. Well, just a might uneasy Being so close to that their Comanche reservation and all what do you mean? Well there to tell you the truth hoppy I told that fella such a dog on good story about them Comanche tortures.


Hi, this is George Cowell. In today's video, I want to talk with you about enrollment. But before I do that, I'm gonna see if I can actually get Buddy to come over here. Buddy is my dog and somebody requested to see him, so let's see if this works. Buddy, come here, and I think he's coming around here. Buddy, come here. I just dropped the treat that I'm gonna give him, but at least you can see him. He's a good boy sometimes. Okay, so I want to talk with you about enrollment. I'd better give him something, actually. I want to talk with you about enrollment, and enrollment is another word for sales or selling. There you go, Buddy got his treat. But a lot of people don't like sales or selling, so I prefer to use the word enrollment to take away some of that fear, because authentic enrollment is simply about finding the right match between your service and the person that you are wanting to serve. The better the match is, the more it's a fit, the more aligned the service is with the person, the less selling you have to do, the less enrollment, the less marketing you've got to do. So how do we find the right fit between your service and the person you're trying to reach? Well, first of all, you got to ask yourself, what kind of person are you trying to reach? And one way to ask that is to look at the people you've already served, you've already given your service to in the past, whether it's existing clients, previous clients, or simply friends. Maybe it's friends of friends, but the people you've already given your service to write down their names and look down that list and ask yourself, whom did I most enjoy serving? Okay, so that's again, step one, write down the list of the names of people you've served, clients, previous clients, or simply friends, or simply people, if you're just starting out, people you would love to serve, people you actually know whom you would love to serve. Write down their names and then write down of the people you wrote down, let's say you wrote down 20 people, which five of those would you most love to serve? Okay, did you most enjoy serving? And what problems did you most help them with? Okay, what problems did you most help them with? I want to introduce some ideas to you here. You want to look at the problem you help them with the most, the symptoms of those problems, or the events that triggered, you know, the them needing to a solution, your solution, or the goal that they're yearning for, that maybe they told someone that they're wanting to achieve a particular goal. Okay, so let's kind of give some examples here. Let's say someone, let's say you are a health coach who helps you deal with the emotional side or the sort of the non-physical side of chronic illness. So an event would be that someone got a diagnosis from their doctor that they have a chronic illness, and now they're worried of what house is going to affect my career, how do I live well with it, and if you're someone who helps them with that, that's the symptom or event that is obvious, that's a trigger for your service. Let's say you are someone who helps people with their relationships. A symptom or event would be that they are complaining to their friends about their relationship, and that's a symptom. And so the question really is how can us, your colleagues, your friends, your network, how can we most easily refer you? How do we know whom to refer you to? So you've got to be clear with yourself, I've got to write these things down. Symptom, triggering symptom, triggering event, problem or goal. And I welcome you to use the comment section of this video to help each other brainstorm what that is for you. So anyway, I hope this video has been helpful. This is just the beginning of the discussion on enrollment, and let me know what other questions you have. All right, so see you in the next video.