That's the signal to YouTube to send me something saying hey, I'm Curtis and I watch you know I don't know basic white girls lip-sync to rap videos and Lulu lemon. Oh, yeah. What's up guys? This is Chris Pike my friends. Call me big C. I'm back in action today I'm back using the heartbeat tool and I want to talk to you about a new Brian Johnson video that just came out and he addresses why the YouTube algorithm Isn't or may not be suggesting your content in 2024 if you want to follow along with me It's h.ki and I apologize if my voice is cracky I'm still a little sick here and I lost my voice, but it's coming back slowly But surely but here we go.  So we're gonna start this one off here Let's click in and let's get going. I'm gonna turn the volume up and here we go. All right. Here we go So we're gonna check out Brian Johnson's video. It's quite a long video But I've selected a bunch of moments that I think are the best moments especially for Smaller YouTube channels and newer users. So it starts off quickly here with why won't YouTube recommend my videos first few seconds This video very interesting. Let's go Why won't the YouTube algorithm? Recommend my videos if you're lucky enough to get views within the first few days hundreds of views maybe even thousands of views Statistically speaking those views probably died several days after publishing Yeah, this is what I like to refer to as the YouTube flat line We've all been here We all know how this is whether you're a large channel and you upload a video and then it just stops getting views or You're a small channel and you get ten views and then in the first few days and then on day three it gets zero views or one view We've all been here. There are ways to combat that which will be discussed in this video in terms of topics and keyword phrases and things like that But yeah, it's definitely worth noting that I think we've all been in this situation. I'm in it right now So let's get forward now to three minutes and six seconds and he talks about the recommendation engine browse and suggested videos Here's why when we talk about the recommendation engine, we're really talking about two algorithms browse and suggested Right. So this is the recommendation engine. This is separate from Keyword this is separate part of me from search terms So whether it's a YouTube search or external search through websites like Google. These are this is totally different It's worth it to keep that in the back your head and both really pay attention to The viewers so think about this when you upload a video the algorithm doesn't push your video out to a huge group of viewers Instead it waits for a viewer to log in imagine. I'm just logging in I I click on YouTube the algorithm right then is gonna say, okay We've got a viewer. What kind of video do we think that viewer is gonna love and watch and really engage with? Right, so this is a very very very important part point in my opinion Traditionally years ago YouTube would put, you know popular videos on the home page And then it would promote them and it would you know, we would try to push popular content out what either You know having a top of the front page and you YouTube or whatever But it's it's gone far past that now machine learning and all that is kicking in now instead of pushing it It's pulling it so when I log in that's the signal to YouTube to send me something saying hey I'm Curtis and I watch, you know, I don't know basic white girls Lip-sync to rap videos and Lulu lemons like that's pretty specific. Okay.  Maybe that's my thing I don't know. Hey, look, it's weird, but at least I'm honest right guys But maybe it knows that's what I'm into for some reason I like basic girls doing basic things and it's gonna pull I'm gonna pull those videos in it's not gonna push them to Me it's pulling them based on my very weird Preferences, okay, I got to get going here that that's too much info. All right, let's go So the algorithm pulls videos for the individual viewer It doesn't take your video and push it out to a huge group of viewers In fact, check this out. This statement comes from YouTube. It's based on a white paper They wrote years ago about the recommendation engine and it's based on user history So it right so, you know when your parents always tell you remember to delete your history. Oh, wait, that was just my dad Yeah, never mind. It says as an example consider the user's past History with the channel that uploaded the video being scored So when that viewer comes on to YouTube and they're looking the first thing the algorithm does is what? Channels is this viewer watching right now and that's gonna pull videos And I want you to think about this algorithm the recommendation engine as having two big buckets Right. So there you heard it there and the two buckets are browsed and Suggested now the next part here doesn't make a whole lot of sense in my opinion So I'm gonna skip forward here, and then I'm gonna go right here to how many videos Have they watched on your channel something else you may want to think about Wait and furthermore YouTube says this how many videos has the user watched from this channel So the more they come back to your channel the more likely the algorithm will recommend your next video, but right, so sometimes some creators for example will do one topic like let's say it's League of Legends and They make great League of Legends videos But it's all about League of Legends and people are always coming back to see the latest build or the latest whatever Those types of guys and gals often get more views than guys like me for example on my other channel I make content about all sorts of different things like video editing, you know Photoshop all these other things AI they don't always come back as much so sometimes You know the number of videos they watch on your channel is very very important. So yeah, just keep that to back your head He talks about new channels and topics But that brings us to this next statement, which makes it possible for any channel size Even a channel that's just getting started. No views. No subscribers Here's how to win when was the last time the user watched a video on this topic, right? So keep this in the back your head as well there's there's the individual channel and then there's the individual topic and a Topic is different a topic is could be done by anybody like I could make a video about the YouTube algorithm Your friend could make one and his friend and his friend. That's the topic. It's not the channel. These are often Well, you'll see Big you see we've got one bucket remember the algorithm is gonna pull videos from one bucket based on Videos and channels the viewer watches and then they're gonna pull videos based on Topics so they could pull from the channel bucket. So I got a favorite channel. I watch all his videos I'm gonna get info from there But I also watch a certain topic and that topic again could be you know basic women doing lip syncing to hardcore rap videos and in You know strange designer Lulu them in athletic of wear like it could be something like that That video those types of videos could be pulled into my stream from multiple channels not just you know Basic girl dot TV for example if you're struggling the more you can honor Topics and keyword phrases the more likely you can grow now. I just got this comment There you go So if you're a small channel, you're not gonna win the I've got a big channel and people watch all my videos Game because you don't or at least it's it's a small part of your business But you can compete on the topic thing or what he calls Keyword phrases and how to target them. Let's get forward and see what his suggestions are around that there So Tony if you want to grow think about keyword phrases So what I like to do is I just think of keyword phrases as topics for example If you search for a YouTube algorithm, that's a topic and it's also a keyword phrase and I'm also ranking number one or Number two, maybe you'll see number three It's based on a number of factors But when I look at an account a browser where I'm signed out of YouTube I know so this is a second reason why you you can use an incognito browser is so if you load up a Google Chrome in incognito mode There's multiple reasons to do that none some of which I won't discuss This one is one that I will discuss and it's great for figuring out where you rank without you being logged in To an account so it'll sometimes give you better results if you're logged in and you're trying to see where you rank So keep that the back your head notice that I'm number one for multiple keyword phrases And you really can't argue what the results that I'm showing you here And what do you think happens as you target more specific topics?  It's when they come in that's when they're gonna get it So it's a poll more than a push although again. It's a little bit of semantics Let's get forward to day two So how date one is all about the polling process day two is more about, you know YouTube measuring and seeing how all the videos done and then deciding whether what to do with it from there And then what YouTube is gonna do is after a day They're gonna measure the performance of your video the YouTube is gonna look at how long did the viewers watch? Did they subscribe a lot of talk about subscribers don't matter I understand why that's a discussion, but the fact of the matter is a hundred percent Beyond a shadow of a doubt yeah when someone subscribes it sends a powerful signal That's right and all of this is coming down to signals if someone Likes your video comments on your video or a positive comment because they can measure sentiment quite easily now especially With all the large language models and all that stuff out there Did they subscribe these are all signals YouTube Google they're looking for signals Subscribing to your channel is a big signal Well to YouTube that viewers enjoy your videos and YouTube is gonna be more likely to send your video out on Day two and this is exactly what happens the performance of your video determines how it does on the second day right so Day one is important day two if you pass day one And you get some good metrics and you get some good signals It goes out into the wild and here he discusses day two and even day three. Let's take a quick look at that If it's good enough YouTube will push it out interesting now on day two of a video release often what will happen is a Lot less of my regular viewers will see the video, but YouTube pushes it out This is I'm excited about day one, but day two is where it's at He's not wrong here. This is right day two is to make or break it because if the video is good independent of what your individual Subscribers or viewers, you know people that come to your channel regularly if it's objectively good and it's got objectively good metrics It'll share it with the world and that's where the big big view counts can come from Because that is when my video enters what I like to call Nightmare mode. This is where your video is pushed primarily to non Subscribers now still you're gonna see subscribers watching But again, it's mostly new viewers to your channel And you have a chance to make a great first impression if your video does good Again, then guess what you make it to day three and YouTube Continues to push out your video to more and more viewers There it is. So that is generally how it works guys It's the the first initial burst is important But each step of the way is important and as you move further down the I guess down the tunnel The better your video is if you get past it it could be shared and that is probably how viral videos are Selected, you know videos just hit all these click-through rates and and and watch times and all that crazy stuff Watch through percentages, etc It could go potentially viral or it can go into the search results where people are looking for things and YouTube will serve your video that's where I personally make a lot of my views and a lot of my money is off that and Yeah, it just works. So there you go guys. This is a great video. You can watch the whole thing I hope you enjoyed the moments I've selected. I've got a ton more videos coming up. Stay tuned. Thanks. What?


Hey everybody, I'm Jen and this is the open source.com weekly top five video We published this article or this roundup as an article and as a video Every Friday afternoon, so I would encourage you to subscribe to our YouTube channel So that you can get an alert that we have uploaded the new video It's also a great way for you to check in with the site and see what's been most popular And then choose from that list the small short list a couple of things that you might be Most interested in reading. I know that your time is probably Precious as it all as it is with all of us. So this might be a great way for you to check in with us weekly Alright, I wanted to also mention that tomorrow is Arduino day on it's every every March and tomorrow It's on March 28th. So a lot of people around the world will be Tinkering with their arduinos and doing some fun maker and tinkering projects So today we published an article that is a roundup of six fun projects that Our staffer Alex Sanchez came up with and so hopefully you'll find some fun in those and maybe even try one out tomorrow All right, so let's hop into our top five this week at number five We have listened to streaming music with pie music box after his project to control his Christmas tree lights with a raspberry pie Anderson Silva wondered what he would do next finally. He landed on tinkering with pie music box It's a spin of Raspbian and Mobidy that allows users to play streaming music services like Spotify iTunes SoundCloud as well as your local sound files This is a step-by-step guide At number four how one professor saved students millions with his shared textbooks Nicole Ingaard interviews David Littman of Pierce College where he is a professor He has saved students millions of dollars with his shared textbooks We all know how expensive they can be and he's also built something called iMath AS It is a free and open source math assessment and course platform. So read more from that interview with them At number three where is the best place online to learn a programming language? So this is another poll another great poll that we ran this week. That's doing well with readers. It is based on our last poll That asked which programming language was the is the best to learn first So this poll follows up on that by asking from what service or organization online Should you then learn that programming language? So Code Academy is out front with Coursera and some written-in responses, which we love close behind At number two intro to grace and open source educational programming language Joshua Holm brings us an article introducing grace and Explaining just how it is designed to meet the needs of teaching and learning programming in an educational setting Holm includes some helpful code as well as a couple of videos to round out his coverage One of those videos includes a talk at a Linux conference by Michael Homer Finally at number one this week how to do fast repeatable Linux installations David Boff has been writing a series for us on what he calls the Linux philosophy There are nine tenets to this philosophy of which you can read more about in his first and second articles This one however is about automating all the things David walks us through how he installs Linux and scripts repetitive tasks Including a link to his fairly simple bash script that he uses to do configurations and installation of desired RPM packages All right, everybody. That's our roundup this week. I hope you enjoyed it and I hope to see you next time. Thanks


This study examined the spatial distribution of macromolecules on live cell membranes at the nanoscale. Using a combination of experiments and simulations, they discovered that they are sharp gradients in the concentration of macromolecules within a few nanometers of the membrane surface. These results suggest that certain regions of the membrane are more likely to exclude larger molecules such as glycoproteins and glycolipids, which could explain why some proteins are excluded from the membrane. This research provides insight into how plasma-membrane biophysical organization affects the binding of macromolecules, which could be used to improve the design of monoclonal antibodies. This article was authored by Daniel P. Arnold, Yashin Xu, and Shou-Shi Takatori.


Everybody welcome to our OpenShift Commons AMA, ask them anything, not me, for Knative. And today we have Paul Maury, Matt Moore, Scott Nichols, and Roland Huss, all participants in this wonderful project who are going to give us an introduction, tell us a little bit about the roadmap, and hopefully leave a little bit of time at the end for all of your questions. So, we are live streaming this, so if you are in any one of the multiple live streams like Facebook, YouTube, or Twitch, or I think Periscope even now, throw your questions in that and we will aggregate them here and force these people to answer them. So without any further ado, Paul, introduce yourself and your cohorts and let's find out what's going on in Knativeland. All right, well, I'm Paul Maury, everybody, and I work on Knative at Red Hat. Why don't we just have everybody introduce themselves so you can be sure that you're satisfied with your introduction, and if you're not satisfied, you have only yourself to blame.  Sure. Hi, I'm Matt Moore, I work at VMware. I'm one of the folks who started Knative now a little over three years ago at Google and I've been doing container tooling stuff for what feels like forever. I'm going to pass the hot potato to Roland. Yeah, hello. My name is Roland Huss. I'm working on Knative I think now for two years and I'm mostly involved in the Knative client project and I'm the working group lead and yeah, I'm doing all the things client here. Yeah, that's me. Now, Scott, up to you. Hey, howdy. I'm Scott Nichols, I work on Knative at Red Hat, formerly Google. I work on the eventing side mostly focused around source creation, so that's how events get into the cluster and make interesting things that you can do with events. And I also contribute to the cloud events, the NCF project. Scott, if I can just correct you, it's news to me if you work at Red Hat, I think you meant to save VMware. I thought I said, well, okay, well, yes, sorry, Red Hat. What? No, VMware. Roland's freaking me out. You know what it is? It's this Red Hat logo down at the bottom here. Anyway, moving on. More show. Moving on. We all work together. Paul, your camera's not on, Paul, so we're not seeing your smiling face. You want to see my face? We'd love to see your face. Hey there, it's me. All right. Yeah, I guess I'll just hold this if you want to see my face. So what is it? One of the things that is sort of in the air in our industry is the confusion between two related but different things. And those two things are serverless and FAS or functions as a service. And I've seen Knative referred to as a FAS a few times. It's really not. And here's how I would put the difference between the two. And any of my co-presenters feel free to riff on me or correct me if I'm wrong or whatever. But I would articulate serverless as being essentially request driven and automatic scale to zero as being two identifying and key properties. So when we think about what FAS is, it's usually a lot more than serverless. I think to me personally, my own opinion, FAS implies serverless, but serverless doesn't necessarily imply FAS. So when we talk about Knative, we're going to be focused on serverless elements. And we're not going to be focused as much on those experiential elements that are the difference to me personally between serverless and FAS. Or FAS is something more than serverless. It's got a lot of connotations of developer experience, builds, and SDLC bound up into it that are more than just serverless. So let's talk a little bit more as I'm double fisting these devices since I've got my phone and my laptop. I'll see if I can operate them both correctly. What is Knative really now that we've kind of maybe close to hit bedrock with maybe if we were thinking it was a FAS we're sort of recognizing that it's not exactly FAS and it's more serverless. Knative is really Kubernetes extension that is focused on developer productivity. So when we talk about extending Kubernetes, I'm sure this will be familiar to a lot of people in this audience. That Kubernetes extension looks like a Kubernetes like API, so declarative API surface, usually implemented with CRDs. And that is what we use in Knative project is CRDs and the accompanying features of cube like web hooks for conversion, for validation, for mutation that provide a Kubernetes like API and API experience. Without adding code into cubes. So we're extending Kubernetes to solve these boring but hard problems like scaling to and from zero and scaling on demand based on requests and having history of revisions for our application and routing events and stuff like that. So things that boring is really not is not being overly generous. We're maybe being facetious when we say boring but hard, but maybe things that you would repeat over and over again. I've certainly implemented some of these things myself in previous lives before Kubernetes. So things that you might find yourself implementing over and over again, they're tough, they're hard to get right. They take a lot of engineering know how to get exactly right. And in my own personal impression, that's sort of the value proposition of Knative is that we're doing a lot of these things that you would have to worry about yourself because Kubernetes doesn't already do them. And giving you the tools to kind of really just focus on your business logic and what you want your application or the system that you're building to do. So there's two key pieces here and actually this this is an outdated slide and Roland I'm just going to apologize to you and the folks that work on the client because I've left off the client but the two key functional pieces that we're going to talk about today and we're also going to talk about the client. Our serving, which is about the like scale to and from zero scale up to end on demand, history of immutable application revisions that we can split traffic between for any number of different reasons that we want to do that. And eventing, which is about connecting in a loosely coupled and late binding way event producers and consumers. I don't want to say too much more about either of these to so that I don't steal the very impressive bolts of thunder that my co presenters have for us today. But that's those will be two of the main focuses and then we're also going to hear about the client. And that's, that is those are the high notes. So, co presenters, do you want to just add anything here before we move on, or is that sufficient for you. I think you nailed it Paul. Yeah, nailed it 2021 off to a good start nailed one thing already. Let's move on to a little history lesson. So, Matt, why don't you why don't you do the first couple bullets here because Matt is is one of the founders of K native project. Sure. So, this is, this is, you know, there's always a lot going on but this is sort of a highlight reel of some of the sort of major events throughout the course of the project so back in sort of fall of 2017. We started some of the really early prototyping of, you know what Paul described trying to sort of look at what higher level abstraction on top of Kubernetes for, you know developer productivity serverless fast fail thing would look like and publicly, you know, we, you know, tons of folks joined in red hat joined in pivotal joined in, you know, lots and lots of folks were, we're discussing it and it launched publicly in July of 2018. And a lot's happened since then so at the time we also had another area called can you to build, which was intended to help solve the sort of source oriented nature that people sort of traditionally think of as being a key part of fast workloads. And in March of 2019 that that's spun out as its own project, which you may know now as Tecton. So, you know, other major milestones the serving API had their v1 revision in September of 2019. And one of the one of the big things that's been sort of a recurring theme laced through some of the more technically oriented things in here has been the topic of sort of governance. And Paul's been, you know, one of the one of the big advocates of this on steering. In May of last year, we had our first to see elections. And Marcus and Grant joined the to see and we now have a sort of vendor neutral representation no one company has more than two of the five seats on the technical oversight committee which was a really interesting milestone and the sort of open aspects of currently thereafter in summer of 2020, the eventing API went v1. And in November of this year, this past year, we had our first steering elections where Paul won one of the elected seats and and I guess was one of the other folks who started the project. A few years ago, one one of one the other elected seats so we now have both a steering committee and a technical oversight committee where no one no single vendor, you know, has all the say, right. So, it's very exciting times for the project. Yeah, one thing that I'll just add is that when Matt talks about the technical oversight committee and steering committee is that in addition to the vendor neutrality element that Matt described the folks on those committees are serving as individuals not as employees of their vendors so in this in the sense that vendor neutral in the sense that like you, we can't have more than two people employed by the same vendor. Those folks that are in the committees are not acting on behalf of their vendor they're serving as individuals, which I think is an important point to mention. Thanks. Thanks for the history lesson Matt. Anybody else want to get critical detail that I'm already thinking for granted. Yes. Anybody else, any of my co presenters want to add anything to this slide. Excellent. Okay. Alright, so we got the first meme of this presentation. Cloud events. I had a couple different variations of this meme. One of them is the one that you see the other one said cloud events I wanted to put Scottie's face on it but I didn't have enough time. I think Dan pop generously offered to do it and then I forgot about it. So this is what you get. Well, maybe make one that's even more funny, but wanted to say a few words about cloud events. I'm not sure how high the name recognition is for the cloud events project, but the cloud event format is a vendor independent standard for event metadata that that is actually a CNCF project. Scott, in particular, I think from the group of co presenters that I had today is very active in the cloud events space. So, Scott, you might want to add add stuff to what I say after I'm done. But the reason that I mentioned cloud events is that when we talk about things being event activated and event driven in Knative and, you know, in particular eventing. There's probably a fairly obvious connection there with eventing. The message format that is the lingua franca of Knative project is the cloud event format. And it is supposed to facilitate interoperability between different producers and consumers and be a vendor neutral format that can be adopted. And it's what we're using as an event format in Knative. Scott, do you want to add anything to that? Anything important that we should know before we continue our journey through this introduction to Knative? I think the only missing important bit about cloud events is that the specification describes how to turn the core nugget of your event between protocols and back to this protocol-less version of that event. And so the reason this is important is I can go and write my fads, have it based on cloud events, and then all of a sudden I'm not locked into the protocol I choose when the project started. So Knative serving is really about, you know, adding this missing layer to Kubernetes to make, you know, functions or containers scale easily. Eventing is really about kind of choose your protocol of how you do transport later, because we help turn these events from these cloud events into other protocols. So you could be running in Kafka in production, but maybe Nats on your desktop because it's a lighter weight to run or something like that, or even pure HTTP. So we get away with this because we depend on cloud events to be this kind of like neutral converter between these protocol-specific eventing formats and this conical form. Right. Well, let's talk about, let's do a little bit more in-depth on serving so we can learn a little bit more about how that scaling works. Matt, I think this is your slide. What does Knative serving get me? Sure. So I think you framed this well at the beginning, right, talking about a lot of the stuff you have to do in terms of sort of, you know, there's a lot involved to launch a production service on top of Kubernetes, and a lot of, you know, I'd use the word boilerplate in terms of the kinds of things you need to set up to sort of operate a service, right? You have deployments, you have services, you have ingress, you have HPAs, you have all of these things, right, that, you know, you need to do when you're adding new services. And as folks shift from sort of, you know, big monolithic applications to, you know, the new hotness, microservices, or even functions, right, you end up needing to do that a lot more, right? And so the way I like to think about serving is sort of reducing the incremental complexity of launching new services and, you know, having this goal of enabling developers to effectively focus on, you know, the business value they want to provide in those services, right? So really with K-Native serving, what you bring is just a container image that has your HTTP-based application in it.  As Paul mentioned earlier, as you, you know, create changes in your application, each version of your application is stamped out as what we call a revision over time. The next slide sort of illustrates a little bit what makes this a powerful concept is, it enables you to reason about sort of versions of your application over time. And this is most useful when you want to, say, canary sending some traffic to a new version of your application or all of the traffic to a new version and roll forwards and backwards in time depending on your production needs.  I just want to make sure I, yeah, okay. And I think the two other really interesting things are request-based auto scaling. So as your application gets more or less traffic, and this may be because you are rolling out a new version or not, we will basically right-size your application and, you know, have 10 replicas, 20 replicas, or even zero replicas depending on sort of the volume of traffic your application is serving. The last thing that we do that I think is really interesting to call out, and this is to enable those sort of fast-style use cases or what folks think of when they think of fast, right? With your lambdas or your Google Cloud functions or your whatnot, a lot of these fast models have this ability to have the sort of runtime layer take care of concurrency control. And so if I want to say only let one request through to each instance of my application at a time, you can do that through this idea of container concurrency. And one of those things that we have built to your application doesn't need to deal with, you know, concurrency control, which can be tough to get right, especially when you start to blend it with things like load balancing and auto scaling and getting really good performance out of some of those things. So yeah, so the next slide really illustrates the resource model here. So I mentioned the sort of one resource that you need to deal with for launching new services. This is the service resource. In its simplest form, you pretty much just give it a container. This exposes an HTTP endpoint. Under the hood, it creates a what we call a configuration resource, which tracks the sort of latest state of configuration for, you know, what is running and those revisions are that history of changes to that configuration resource.  And so, you know, as you make changes to your branch, new commits happen, but the old commits are always there and so you can always sort of reference those older commits if you need to. And so the route is what controls where traffic is spent over that history of configuration of revisions. And so you can either have us automatically track the latest or you can, you know, if you want to sort of take complete control, you can, you know, control percentage based were allowed to, you know, to distribute traffic across some number of revisions.  You can even do 0% splits and do what we call tagging if you wanted to sort of pin but qualify a new revision prior to sending it any of your sort of main traffic load. So you can do some very powerful and sophisticated, you know, canarying and qualification prior to rolling things out. But the configuration to do these things is ends up being typically quite quite small. And so we take a lot of the complexity out of some of these things that, you know, can get very, very complicated. So next slide. I think it's our next meme if I'm not mistaken. Okay, yes. So this is this is my favorite bit of a native flood right so when we first launched this was actually true. We did actually need Istio but one of the pieces of feedback we got pretty quickly was that. You know, there are other networking layers out there. You know, some folks don't want sort of the full mesh style networking layer some, you know, just want to deal with, you know, ingress style networking and so one of the things that we did was we built an abstraction between sort of that sort of describing what we need from the networking layer where, you know, Kubernetes ingress wasn't quite cutting it and I think everyone has sort of accepted that to ingress v, you know, now v1 it was v1 beta one at the, you know, at the time and for what seems like forever. But so we built an abstraction that, you know, let us describe sort of our needs from the networking layer. And Istio became one of those options that we have now half a dozen or so integrations like career and contour and glue and Kong and ambassador. And these are all in our sort of install instructions and frankly I, you know, I'm partial to contour but like I haven't run Istio in, I think over a year for most of my native development and, you know, it really it's just an implementation detail and you can choose any of those options and a lot of them are actually, you know, really great and I think, you know, comparable to Istio which is our oldest integration. So, so yes, we do not need Istio, Istio is just one way of running Knative. Do you want to add anything to that Paul. You know, the thing that I wanted to add before we move on is just that, and I don't think we touched on this but it's important. The service API and configuration APIs are subsets of the pod spec. And so when we see the demo later in our talk. Let's let's just make it make sure that we highlight that so that people can see it in action. The reason I mentioned it is because I suspect that a lot of a lot of deployments that people have today would translate directly into services if folks wanted to try that out and see how their existing deployments can invent driven mode where they're scaled down and back up depending on load. But otherwise, I think you covered it very thoroughly. And I will just go ahead and advance the slide now to the roadmap. Okay, so this is this is a sort of case of some of the things we're working on. Excuse me, sorry, I had to tickle in my throat. So see, these are some of the things that we have sort of cooking in various stages of development. One of them is domain mapping the idea of being able to assign sort of a vanity URL to your K native services so you don't have that food up our example.com you can have like, you know, my awesome blog dot map more.io.  So this is an alpha I believe it's available in our dot 19 and our dot 20 releases which want dot 20 is not off the presses dot 20 added auto TLS to it. This is an alpha API. So if folks want to give feedback on this, we would really appreciate it. It is magic, by the way, it's, it's one of the coolest features that K native ship in a long time. I am so excited about it. Basically what it results in is TLS terminated pet project domains across your cluster. It's amazing.  One of the other really cool things that I like that's been this has been in the works for a few releases now is this idea of gradual rollout. So we support very fine grain traffic control where you can, you know, take revisions directly and split across them with pretty fine grain. But one of the most common modes we see folks doing and this is, you know, when you're getting started, you sort of just want to roll out to the latest all of the time. But depending on how much traffic you're getting if we just shift things over in one big swoop, you know, our ability to scale from zero to, you know, huge number might be, you know, limited by factors at the Kubernetes layer. And so what the gradual rollout project is doing is basically making it smarter about sort of being able to shift traffic to that over some amount of time that you have specified.  One of the last things I wanted to touch on, you know, I mentioned that networking layer that we created as our own abstraction because Ingress V1 wasn't quite good enough. We've been engaging with the Ingress V2 efforts in upstream Kubernetes to make sure that when that lands, excuse me, when that lands, it does meet our needs and we can retire that abstraction and leverage, you know, just raw Kubernetes to do a lot of what we want. And then two aspects that we will be sort of pushing on forever are scaling in every dimension you can imagine, as well as request latency. So I will hand things I think back over to Paul. I think that's my... Yeah, we've got a couple questions about serving in the chat here. The first one is from Dan. Can this integrate with Helm for deploying Helm charts, rolling back charts, or does it replace it? So I just want to make sure I understand. So I think the question is, can I use Helm to roll out KMATive services? Is that the gist of it? I kind of had a different reading of that, but I think the question that you read out of it is an important one to answer. Sorry, can you guys hand me that one first? Yes, go ahead. So yeah, I mean, that is an alternative reading, and that's fine, I'd like an answer to that as well. But it was more, I saw you talking about the way that you've got this idea of a canary, a rollout and a rollback. And I kind of... We've been expecting to use Helm to do that, and I'm just wondering, is this an alternative? Because we've committed quite a bit to model our applications to be deployed as Helm charts, and I just wanted to, does this integrate with it, or does this replace it as a mechanism for rolling and upgrading between versions of services? So that's a good question. So I don't think we do anything specifically to integrate Helm more deeply than what you can do with Helm and our YAML, and you should be able to use Helm to roll out canary services in much the way you can roll out other resources. But I think we haven't done anything to sort of integrate with Helm more deeply with respect to awareness of its revision model. But I think in principle, nothing stopping you from leveraging Helm to manipulate K-native's concept of traffic control. One of the things we did introduce is we have this more sort of sophisticated way of sort of doing fine-grained control where you can rather than just having us generate names for each new revision, you can bring your own name for the revisions, which allows you to sort of predictably stamp out new names for revisions, which you can then use in traffic control. And so that allows you to do, I think it allows you to do more like what you were describing, but there's no deep integration if that's the question. And so would you expect to deploy different revisions to different namespices, or would multiple revisions be deployed to the same namespace? Typically, there's a best practice kind of thing. So today, all revisions need to live in the same namespace, and most of the resource model within serving expects things to live within a single namespace. And to some extent, it's designed so that if you were leveraging namespaces as your tendency model, you should be able to hand users credentials to manipulate K-native serving resources within that namespace, and they should be able to operate productively, if that makes sense. Okay, great. Thanks for your time. There's one other question that I'll call out for now. It's not the only question in there, but it's the one that's closest to serving. And the question is, will, let's see, when is there an ETA on functions coming to K-native? And I would say at this point, there really is not an ETA that we can give. We had, like in our community, we had maybe a couple times the subject has come up, but we so far haven't, and I think there's a very great interest in having a concept of functions that is on top of K-native that's community-based. But we so far haven't been able to agree, I don't think, on an approach. So I can't really give an ETA now. It's definitely on our radar. And I appreciate the question being asked. I think what would be great from the, if the person who asked the question is very interested in it, I'd love to get a note about that to the K-native dev or K-native users mailing list. They're K-native-dev and K-native-users, and it's home in Google groups. I'd love to get some surfacing of that in there. I will definitely surface that it came up, but so far we can't really give an ETA on it. And I think in the interest of time, it's probably best to advance the slide now, and I think that will be eventing.  Thanks, Paul. Okay. So what is a K-native eventing get me? That's a good question. I can read the slides here. So we're enabling async app development through event driven from anywhere, loosely coupled and late-bind producers and consumers, producers generate events before consumers exist. So basically, eventing has a hard problem because there's, you know, 20, 30 years of eventing history in compute, right?  But eventing patterns and messaging patterns have been around forever. So we kind of got to step back and say, what does this look like in Kubernetes land? And the answer is something that is late bound. So you have a reconciled loop that's constantly healing your consumers and producers and repointing them at, you know, my consumer moves to a new cluster URL or a new cluster or it resolves to a new address or gets deleted and recreated somewhere else. And that being able to heal the cluster's eventing mesh is something that we really focused on around in eventing. One thing the slides don't really say is eventing's really broken up into a few different big major chunks. We started out with messaging. We have a messaging API group and it kind of, it puts a thin abstraction on top of, like pub sub components. Turns out that's really hard to build with because it's very imperative on how you would assemble your cluster. So we came up with a second model that sits on top of that, that can leverage it, but it doesn't have to, we call eventing. And eventing is more like, actually, can we go to the next slide? Can we kind of show? So we, eventing brought in this thing called the broker. You can think of this as like the ecosystem or the mesh of all the events that are flowing through your eventing system. You pluck events out of that mesh using a trigger. Trigger points to a broker, has a filter. You could consider it like a query. Once that query matches, that event gets copied out of the broker and delivered to a subscriber.  Now, one, one thing that I'll just mention here is that the, the targetable doesn't have to be a K native service, right, Scott? Yeah, yeah, okay. So the, as we were developing of eventing components, we kind of had this idea, I think, Vile and I were talking to Matt and we hit upon this idea that will potentially K native serving. We don't, we don't want those components to be coupled, right? So eventing knows nothing about serving. It's independent, but they do share some common interfaces that we call duct types. But basically, the trigger can point to this duct type that we call addressable, which basically says in your status, you have this place that you'll expose your URL you would like to be invoked on, right? So anything, any CRD could actually implement this. And a lot of the eventing components implement this contract. Serving implements this contract. You could write a CRD that implements this contract and have it just kind of wire up and play. Or the trigger takes a URL to, which could be in cluster or external to the cluster. So, yeah. This K native eventing is completely decoupled from serving, but it works really well with serving. All right, ready to move on to the roadmap slide? Sure. So eventing's roadmap, we're working on stabilization. There's a lot of features that they work, but they could use more tests, and those tests could be a little more stable. So we're really focusing on that right now.  So because eventing's been around and serving, sorry, eventing and messaging have been around so long, there is a lot of ideas around what we, where should we go and what should we do. Eventing doesn't really want to have to take an opinion there. It's, we're trying to enable all of the A star patterns that you could invent and implement using this thing. So where serving brings you really easy Kubernetes gale to zero containers, eventing enables this really easy shim on top of other protocols to help you decouple your choices so that you could make different choices later without having to recreate your entire application, right? But that, that thin shim needs some more features like maybe some smarter filtering in the triggers or improving the reply contract. So like, how do I know in the data plane that if I'm going to invoke some subscriber, how does that subscriber understand that it can reply to the broker to re-engress and invent back in? So why would you want to do that? Well, we had this interesting thought. What if the broker allowed you to reply to events and then those new events that you're replied with gets ingress back into the broker so you never have to know which broker invoked you, right? So smaller footprint, smaller, more reuse of your deployed components, things like this. We are in eventing... Sorry, I thought you were done. Go ahead. So then in the next six months, we're still catching up on the auto scaling of the eventing components. Still working on that. We're partnering with projects like Cata to look at, well, pole-based scale models, maybe Cata is the way. And so we're adding hooks and plug points and some standards on how you get your eventing components to scale with external things like Cata. We're looking at, well, so we make CUBE events to understand what's going on. And we make these cloud events that are in the data plane that your application is making. But we're kind of looking at, well, maybe there's this third category kind of in the middle of what would my application say if it could make events and then how would I route those things and react to it? So event driven models for your application and all of the components that enable your application is this. And... Cainative eventing is... It's kind of an implementation of the cloud events specification with a bunch of other opinions. One of the things that we're working on in cloud events is the discovery and subscription APIs. And I think you're going to see that trickle down into Cainative in the next six months or so. Well, thank you, Scott. Roland, you're up. Why don't you tell us about that fly CLI? Yeah, sure. Yeah, the CLI actually. This is a component which opens you with the door to Cainative Wonderland. So if you go to the next slide, please. It's really about how you can access Cainative from your CLI actually. Of course, you can do everything with your source files as well, but actually a dedicated CLI for Cainative has some advantages. So you can distinguish between two modes of a Rundee. So one is the imperative mode so that, as you know, from Qt Control as well. And you can actually manage nearly, I think, all of the Cainative core entities which are user-facing directly with quad-operations so you can create them. You can make updates and, of course, list them in varied details in a human consumable format. And of course, you can delete them as well. So you can group them also into different areas like we have for Cainative serving. We know how to manage services. We can create, manage Cainative services and also revisions. And also for eventing, we have different, yeah, for every entity, you have kind of a noun so it's all with the same schema. So you have a KN, then you have the noun and then the verb, what you want to do. For the sources, actually, this is also a very important eventing component which is kind of an adapter which main purpose is more or less to convert custom or events from outside into a cloud event format and which are kind of feed into the eventing infrastructure. So for that, we have also direct support for all the sources which already come directly built in with Cainative eventing, sorry. But we can also manage other sources which we can leverage by using plug-ins.  And then finally, you can also export all the stuff that you have done from the cluster into a file. And then actually also just take this file to another cluster and import it there or create it like this group controller also with Cain. But there's also this so-called declarative handling of Cainative services which allows you really to describe your target state that you want to have. And this has the same semantics like cube control apply, which means you have get a three-way merge with the stuff which happens in the meantime between two runs of apply, for example. So it includes the same way and actually it even reuses the way how cube control does this merging. And also borrowed from the cube control architecture is the plug-ins that are similar to cube control. There's one thing which is, I think which is in addition to the way how cube control handles plug-ins. So plug-ins include control just external programs which are executed by executing it from like a comment. So it's a separated process for that. But you can also create in-line plug-ins, which means if your plug-in is written in Golang then you could also make a separate own build of KN and then inline it. So this is quite nice if you want to have kind of a single binary which includes a certain amount of plug-ins and we are currently working also on a cube on a KN builder project which allows you to declare the plug-in that you want to include and then just run that and you get just one blob of binary that you can execute with all the plug-ins included. This of course only works for Golang but the regular plug-in architecture works for any language of course. Then we also added recently Github support as we call it which means we have dedicated tecton tasks that you can reuse in the tecton pipelines for deploying your creative services and brand new, fresh from the press is an offline generation of resource files so you can actually operate KN against your local file system so you do not need to have a direct connection to your cluster but you just add an option minus, minus target you provide a directory or a file name and then it just creates the resource files directly from the arguments that you provide to KN. So this is a very easy way even if you do not have a cluster at hand but you also do not remember the schema of the KNative services of the KNative resources then you can just reuse KN use the help messages and use some arguments and this will build up for you the YAML files. This is very, very convenient and then of course you can take that file commit it into your source control management system and go ahead. This is very, very nice so we just have the support for KN service create but actually we are also continuing this theme by adding it to update and to list and so on. So really this is really a very which I'm pretty excited about. Yeah this is a nutshell is what KN can do for you actually it's really you can everything it can do with resource files as well but it's much, much more convenient in my opinion that you can use KN on the command line you can install it easily with Broom with your Mac on S or Linux you have also Broom for Linux support you can download it from the GitHub release pages and they are released in the same cadence like the rest of KNative so in the six weeks cadence of KNative components and because I just saw the question whether KNative CLI is stable I can say that it's pretty stable it's a little bit for KN it's a little bit different because it supports eventing and serving and so for example as there was some point in time where serving was stable but eventing was not and in this period we had support for both of them but we marked of course the eventing support kind of experimental we also have other features which are marked experimental but otherwise KN is totally stable it's included also in products like an open shift it's already shipped with that and you completely rely on that yeah that's a KN in the chat yeah go ahead let's hear about the roadmap and there's a question that pertains to this that I'll give you once you go through this stuff okay cool yeah what are the roadmaps in the future we of course want to continue on all the topics that we have started we want to support more sources and we also want to support arbitrary sources of sources that are not known when KN was compiled or built and we want to leverage metadata that are offered to us so like CRDs but also the the KNative Discovery API which is easier to consume for us because CRDs are a little bit hidden and typically only meant for administrators so a regular user is not necessarily able to read CRDs and based on this meter information we want to support different command line arguments so we really want to offer dynamically command line arguments that are based on the type that you are managing so this is kind quite challenging but actually this will give you a nice use experience I'm pretty sure then another thing which I'm very excited about I also called Camelette so if you don't know Camelette then no problem because it is really brand new technology it's based on Camel which is also an enterprise application integration platform and the good thing about it is that it comes with around 300 plus components that you can reuse as KNative sources which means they can connect to external systems and even if you don't know nothing about a using Camelettes you can leverage all this existing stuff directly and just use this KNative source for example to connect to systems like telegram sales for service now whatever you want to and Camelettes will convert all these events to cloud events and yeah so support for that will be implemented as kind of plugins as well and then of course we always are looking for new plugins in the KNative sandbox so KNative sandbox is kind of a mating port or something extension which is not really part of the KNative core directly so it's really something where we also put different KNative plugins into and two of them will be a lock plugin which allows you directly to print out service logs like you know from Stern for example but also another plugin like directly creating events locally on the command line and injecting it into the eventing infrastructure which is very convenient for testing and debugging and finally and we are always trying to improve here is user experience but we also rely on your feedback for that so actually we know some weak points in the user experience for example the way how we can specify traffic splits which you can definitely do with KN but we feel this can be better and yeah so we are going to improve on this story and yeah so this is the roadmap which we will work on in the next six months I would say alright thank you very much you know listening to this stuff that we're all talking about in this presentation I'm like this sounds pretty cool but will it blend the Scott I believe you got a demo you're going to show us to establish whether or not it will blend here's where I will shut down the screen sharing and Scott go ahead and you can share your screen and we'll come back to this deck in a moment okay here we go you need to turn it off there we go alright I only got a few minutes so you know I'll just use this brick and extra effort cool okay here we go so I have been talking to my friends over at Falco if you don't know what Falco is it's a thing that watches this events that are interesting and turns them into web hooks there's this other project called Falco sidekick which turns those events into some other thing and I was like well you guys don't really have cloud events there and so I helped them at it and here's a demo of using Falco and sidekick to do some stuff so so let's see first off let's take a look at the graph here so in my cluster right now I have sync binding that links the Falco sidekick into the ingress of the broker so remember the broker only consumes cloud events so cloud events are going to bounce around in there and then I have this trigger to send anything that's from Falco.org with the type of Falco rule output to this sockeye service so what the heck is sockeye it's another fish program I wrote it just shows you the stream of cloud events that are invoked using a web socket between the cluster and this web browser so what can we do we can let me just grab this little exec here so I'm going to exec into my SQL pod that I have running you can see it right here so I'm going to exec into it I'm going to do an interactive terminal cool I've got one and I also got this event here that says terminal in shell that seems like an interesting event I don't really want people to have interactive shells on my cluster here so so I made a very, very, very simple application all it does is it listens for a cloud event and it it does a kubectl delete on the pod that comes in very simple and to implement that I get some R back to allow me to get and delete pods I wrote a k-native trigger that says for things from Falco with that same rule with the rule text terminal in shell send it to this drop service which is a k-native serving service and the yaml for that is here so a couple things to note I'm asking for it to be only cluster internal because I don't really want to expose the pod killing device to the internet, that would be real bad I'm going to show you because of hard mode co-inaction so here we go, we're going to deploy that one thing I'll just add as Scott is doing that is if you look under the template part of the services spec that is in the top pane there on Scott's display you can see that this looks pretty close to a pod right Scott? No, it doesn't look like a pod it looks like a deployment pods don't have the template under the template field if I change this to deployment and the correct and then add to the bunch of other like a Kubernetes service and some other stuff then I would have the same setup it just wouldn't scale to zero it wouldn't have auto TLS so I can see that I've got my drop thing it's cluster local it's ready to go and so now let's go and exact back into that fun SQL pod and we oh, so what happened here the Falco detected that somebody created this the terminal in shell we got another event here terminal in shell if we refresh graph we can see what the new graph looks like so we still have the Falco sidekick ingressing to the broker we have another trigger for drop for this canative service so now we can see the event stream that's coming through the broker but we can also cherry pick that the this terminal in shell and send it to the drop service which goes and invokes death onto my my interactive shell that I maybe I'm trying to do some malicious things I whip this up super quick it's not a ton of code I got to show you which is cool any questions we'll send it back all right thank you very much I'm going to share my screen again now we'll just wrap the remaining slides of this deck up there we go okay will it blend it blended so that was good let's let's talk about 2021 girls real quick as we're we're running over and I thank everybody that's still watching so number one my own personal opinion here is that we have the canative apis are at a v1 level and v1 meaning you know good expectation of backward compatibility I think that for me in my experience getting a project to a 1.0 level is a very important psychological threshold for adoption and you'll see adoptions also on this list so for me personally I'm hoping that in the first part of 2021 that we can declare that canative is 1.0 we also I think are really interested inside the community of folks that develops canative and having more integrations and the one that Scott has just showed us is a really great example of the type of integration that I'd like to see you know the more things there are that spit out cloud events and can consume cloud events the more utility canative is going to have for everybody so if we think about how do we make something that is most useful to everybody the more integrations the better and Matt I think you put the improved UX on here so I'll let you speak to that yeah sure so one of the things that we've started to do is there've been a bunch of sort of user interviews where we've been talking to folks looking to get started with canative and rumblings that we might start a user experience working group to sort of look at getting started as I think is one of the really important sort of journeys that a lot of users take and we want to look at a bunch of these and make sure it's as streamlined as possible so that we can get folks from the point where they have a blank cluster and they're like I want to try out canative and get them to that sort of aha moment like this is what canative does okay as quickly as and easily as possible so that's what I meant by improved UX sorry I just threw it on there before yeah no problem of course we want more adoption and I see there's a question in the chat from from somebody on YouTube any update on how serverless is being adopted in the community these days and I can speak from the numbers that we track for open shift serverless which is the red hat product derived from canative that we saw pretty good adoption growth in 2020 but my own personal opinion and this is why more adoption is on our 2021 goals here I think that in general serverless is still a fairly advanced topic and you know if you think about the growth of the Kubernetes community that kind of looks like a hockey stick right and what that tells me is that if we think about the appetite for advanced topics that probably there are still a lot of folks that are beginning their Kubernetes journeys right now I expect the demand and adoption opportunities will grow and it's coming from the frame of mind of somebody who's serving on steering and wants to help grow the project I think there's a lot more adoption out there to get us so that's definitely something that I think that will work a lot on in the community and we also really want to grow the pool of contributors so I'll just take this opportunity to say you know if you're if you're watching and you think that this project sounds interesting to you and it might be something that you would be interested spending your time on however much time you had to give I would just say that like I think we have a really great friendly community in Knative and we're also really interested in growing the pool of contributors so I would just say like if you have any thoughts about you know you want to contribute but you're not sure what you could do maybe you're not as focused on code I would just say that like I think that there is something for everybody to contribute in open source and I'm really interested if you have the urge, if you have the interest, if you have the desire to contribute but you're not sure how you could do it I would love for you to ping me and talk to me about it you can hit me on Twitter at Cheddar Mint and you can also get me PMORIE at redhat.com and I'd love to talk to you about how you could contribute we definitely could use your help and it's a lot more you know when I think that probably in this audience like there's maybe an unconscious bias toward thinking of like open source contribution as being all code and that's just simply not the case so if you can if you can read documentation and tell us what did or didn't work for you from that documentation that's contribution that would be very valuable for us writing docs participating in things while you're going on pop over to the landing page for Knative so people know where to find the whole project sure it's a very easy it's a very easy URL to remember it's Knative.Deb Knative.Deb and that's a good jumping off point to find any number of things some of which are on this next slide here our Github organization is called the Knative organization there's a link in this slide that you can click when we share it and I'll share it later on on Twitter and some of the other channels that you might be looking at for these things so you can click that link but again you'll find that from Knative.Deb and I think someone else trying to talk go ahead yeah to join the Slack it's slack.knative.Deb that'll get you an invite code to come hang out with us I put the wrong URL on there I believe that is the Slack workspace the other URL slack.knative.Deb will get you an invite link you can also ping me on kuberneteslack matmourn.oe and I'm happy to share invite codes too if folks need them I'll annotate this and correct that slide and I'll upload the video to the OpenShift Commons shortly and tweet that out with the slides so with that I think we need to end and wrap up and respect everybody's time and really thank you all for coming and all the work that you do in the Knative community it's wonderful to see your faces I think each one of you probably could do an AMA on your individual topics so we probably will have you all back in the coming months so thanks again for participating and we will be back again with another AMA next week on a topic to be decided still so thanks Paul Matt, Scott and Roland be safe everybody and take care thanks a lot for having us have a great day everybody bye bye


All right, Bolo Buddies. We are going to be untangling this tonight. It should be a great time. Hope to see you at the show. Also have a few pre-built lots that you can check out by clicking on the house under the auction. I'm gonna be running those tonight also. And I'll see you tonight, book market. Thanks for watching.


Well, good afternoon, everyone. Just a few things here at the top, and then we'll get right to your questions. First, let me start by echoing what you heard yesterday from the president regarding the US-Japan alliance. Quote, over the last three years, the partnership between Japan and the United States has been transformed into a truly global partnership. The relationship with Japan is powerful proof that in investing in our alliance and raising our collective ambitions, we yield remarkable results, end quote. Our defense and security ties with Japan form the core of our alliance and are the cornerstone of regional peace and security in the Indo-Pacific. Recognizing that the alliance has reached new heights, we plan to further bolster our defense and security cooperation to allow for greater coordination and integration. I would add that yesterday you heard news on dozens of deliverables for the alliance. I don't have any more specifics to provide today in terms of timelines and outputs, but we are working hard across all levels of the department to deliver on the agreements made by our national leaders, and of course doing so in very close concert with our Japanese allies. Secretary Austin participated in the events with the Japan State visit yesterday and returned to the White House today to participate in the US-Japan Philippines Trilateral Leaders Summit. The United States, Japan, and the Philippines are three closely aligned maritime democracies with increasingly convergent strategic objectives and interests. Just this past week, in fact, our three countries in Australia held joint naval drills in the South China Sea. Separately, Assistant Secretary of Defense for Indo-Pacific Security Affairs, Dr. Eli Ratner and his team are hosting our Korean allies today here at the Pentagon for the 24th US-Korea Integrated Defense Dialogue. The dialogue involves a wide range of comprehensive discussions about how the United States and the Republic of Korea are modernizing and strengthening our alliance. We'll have much more information to provide this evening when the meeting concludes. And staying with the Philippines, tomorrow we look forward to welcoming His Excellency Ferdinand Marcos Jr., President of the Philippines, and Secretary of National Defense Gilbert Tedoro here at the Pentagon. Secretary Austin will host President Marcos and his delegation to discuss regional security issues to include our shared concerns on PRC, coercive actions in the South China Sea. And in recent news, we were very sad and learned about the loss of two Philippines Navy pilots in a tragic accident. Our thoughts are with their families and their Navy, and we're ready to assist if needed. In light of the engagements I've outlined, and as we continue to advance a shared vision for a free and open Indo-Pacific region, it's been a tremendous week of progress with our allies. And finally, Secretary Austin spoke with his Israeli counterpart this afternoon, Minister Galant, to discuss the current situation in the Middle East and to reaffirm the U.S.-Ironclad commitment to Israel's security against threats from Iran and its proxies. We'll have a full readout of the call available later today. And with that, I'll be glad to take your questions, start with Associated Press's leader, Bell Dolar. Thanks, Pat. Can you bring us up to date a little bit on the JLOTs? The Secretary said earlier this week that he expected it could begin initial operations the third week of the month, which by my calculation would be next week. So have they even started to build anything yet? Can you just tell us where that stands? Sure. As you know, we announced on 8 March that we estimated that JLOTs would be in place in operational approximately 60 days. That continues to be the case. We estimate that JLOTs will be operational in late April, early May timeframe, which of course is within that 60-day window. We're obviously working as fast as we can on that effort, recognizing that any operation can be affected by multiple variables, but our forces supporting this effort continue to stay focused on the mission and the important tasks that they've been given. So again, we'll continue to provide updates. But to answer your question, no, there's been no construction in the water at this stage. So was the Secretary wrong when he said the week of the month? Again, we're working towards having it operational toward the end of the month and early May. But not what he said. We're not to the third week of April yet. We'll keep you posted. Okay. All right. It's a quick follow on JLOTs. When it becomes operational, should it be able to move the maximum number of truck loads or loads of goods immediately or is there some ramp up process, some sort of testing process that needs to happen that will further delay its ability to really have an impact? Yeah, so, you know, as I understand it, essentially, you know, you'll see sort of a phased approach in terms of initial operations capability and the ability to receive humanitarian assistance. But of course, you know, based on various conditions that commander set to achieve full operations capability, you'll see that capability ramp up. Again, as we get closer to the initial operations capability and having the peer go operational will certainly provide much more detail. Thank you. Thank you, General. So I want to go back to the call today between Secretary Austin and Mr. Galant. Today, USAID administrator Samantha Power confirmed the assessment by the IPC that there's famine in North Gaza. The Israeli government made a commitment to open crossing in the northern part of Gaza for the flow of aid. Did the secretary get a clear commitment or a date from Mr. Galant on when this step will happen? And how satisfied is he with the government of the Israeli government basically implementing what they promised to do? Yeah, well, as it relates to today's phone call, as I mentioned, we'll have a full readout on that. So I'll wait for that to come out. But in general, and you know, to include the most recent call he had last week, the secretary does continue to talk with Minister Galant about the importance of ensuring humanitarian assistance can get into Gaza. And so I think some of the initial steps that we've seen in terms of ramping up the number of trucks that can come into Gaza is a good step, but I think we want to see much more. And I think we'll continue to have those conversations, not only within the Department of Defense, but I know that's also happening elsewhere throughout the U.S. government to see those concrete steps about Israel's commitment to get additional humanitarian assistance into Gaza. On a separate topic, but the issue of Iranian threat, as you mentioned, we've seen reports yesterday, specifically yesterday, that Iranian attack on Israel is imminent, that's in response to Israel targeting of the Iranian consulate in Syria. How concerned are you that the Iranian might follow through with their threats? And are you seeing any indications that this is what they intend to do? Yeah, well, we're certainly monitoring the situation closely. I don't have a crystal ball and I'm not going to get into specific intelligence. I would just say that what you heard the president say, and as I highlighted in my topper, we are in close contact with the Israelis to include today's phone call with Minister Galant and that U.S. commitment to Israel's security against threats from Iran and its proxies is Ironclad, and I'll just leave it there. Let me go to Idris. Yes, to the State Department put out a statement saying that Secretary Blinken had spoken with Defense Minister Galant, given that he's Austin's counterpart, Secretary Austin's counterpart, was the Secretary on the call? He was not, but it's also not unusual that Minister Galant and Secretary Blinken speak. So as you know, when Secretary Blinken travels to Israel, he's had one-on-one meetings as well. Secretary Austin talked to any other foreign ministers? On occasion, depending on where we're traveling, and as I mentioned tomorrow, for example, you've got President Marcos, who's the president of the Philippines coming. So a lot of it just depends on the specific topic. If it's foreign policy or diplomatic issues versus security assistance issues. So the bottom line is, when it comes to our relationship with Israel, there are not necessarily going to be, I'm not allowed to talk to that person. You're not allowed to, you know, it's going to be full, robust communication. And you know, when they've spoken most recently or last week, they talked about the world central kitchen and the strike that killed the aid workers. Now you've had time to look over their investigation, their initial report. Are you satisfied with it? Is that something you endorse? Their initial findings? Yeah, thanks, Ejrus. So, you know, you probably heard the national security advisor, Mr. Sullivan, talk to that earlier this week. As I understand it, that continues to be under review. So I don't have anything to provide to you from the Department of Defense standpoint at this point, other than again, Secretary Austin made very clear in his phone call with Minister Galant that we expect to see, you know, concrete actions to be taken to prevent another strike like that from happening in the future. Tom. Thanks, General. Was General Karela in Israel today? Is General Karela in Israel? Yes, General Karela is in Israel. He's, as I understand it, traveling throughout the region. So certainly would be free to send com for some more info on that. If Iran is to strike a target inside Israel and with the, you know, we talked a lot about, you've talked a lot about the ironclad, you know, commitment to Israel. Would the Pentagon be obliged to join in to respond? Yeah, I'm not going to get into hypotheticals. You know, again, I've highlighted our ironclad commitment to Israel's security. And then on a different topic, Monday's the anniversary of the start of the Sudan civil war. Do you have any observations on that conflict? And do you have any, excuse me, assessments of Iran's role in it? I really don't. Again, I will take that question for you because I know you had a question on that. Let me go to Anne and I'll come down here. So on JLOTS, there are a lot of A-trex being allowed into Gaza. Is there any point where JLOTS would not be deployed because you feel like the ground routes are sufficient? And then I just want to try again, if there is an attack on Israel from Iran, can we expect a U.S. military response? Again, not going to get into hypotheticals, Anne. I've underscored our commitment to Israel's security in terms of would JLOTS still be needed if there's increased aid on the ground? At this point, we have a mission, we have a task that we've been assigned, which is to implement JLOTS to help increase the flow of humanitarian assistance into Gaza. And so we're going to continue to stay focused on executing that mission. And we'll keep you updated if anything changes. There's no point at which you have to commit to actually building it. As far as you know, it's a clear timeline you're just moving ahead. Yeah, I mean, we obviously, as I mentioned, we have a timeline that we've set, as in any operation, particularly one that's going to be conducted in a combat zone, there are variables which could affect that timeline. But as of right now, as I mentioned to Lita, we are on course to go operational at the end of the month, early May. So I'll keep you posted, Eunice. Thank you, General. You said that you're not going to speculate on anything when it comes to the U.S. response to possible Iranian attacks inside Israel. One U.S. senator suggested today that there be joint U.S.-Israeli strikes against Iran if there were such attacks against Israel. Are you ruling out anything at this point? I know you're not speculating, but is a joint U.S.-Israeli strike ruled out in this department? You know, look, from the very beginning of this conflict, the Department of Defense established two key objectives, you know, among four, which I've discussed before, but two of those objectives have been to protect our forces and our citizens in the region, as well as support Israel's inherent right to self-defense, and so that hasn't changed. And so as we monitor potential threats and as we do, we'll continue to take appropriate steps to include any necessary force protection measures if our forces are threatened. But when it comes to, you know, speculating on when and if Iran may attack Israel, again, I'm just not going to get into speculating or discuss intelligence. And again, I'll just underscore what I said, that our commitment to Israel's security is ironclad. One quick follow-up if I may. If Iran attacked Israel, would that be considered an escalation or retaliation by the DOD? Yeah, again, I'm not going to get into hypotheticals. Let me go to the phones here. Jeff Schogel, task and purpose. Thank you. The Navy released a picture today, this week showing an O5 firing weapon with the squad common optic backwards. Is DOD considering ordering sailors to go through any kind of training on the fundamentals of firearms and small arms in the wake of this? Yeah, thanks, Jeff. I'd have to refer you to the Navy for any questions regarding training. Thank you. Let me go to Jared Elmonador. Hey, Pat, my question's been asked, but I might try it a different way, I guess. Following the Secretary's call with Defense Minister Galant, you know, the U.S. is committed to Israel's security. Part of that is reestablishing deterrence if that need be done. How confident is the Secretary that Israel is also committed to the security of U.S. forces in the region and the sensitivities around that? Yeah, the Secretary is very confident of Israel's commitment to the security of U.S. forces. I mean, as you know, Jared, we have a longstanding security cooperation relationship with Israel to address, you know, multiple threats throughout the region with the primary aim being regional security and stability. And so I'll just leave it there. All right, let me get a couple of other folks here. Tony. Go to Ukraine for a second here. General Kavele in the last couple of days has painted a very bleak picture of Ukraine's chances for success if the supplemental doesn't pass. I want to go back to the arcane issue of a plan B, the $4 billion that the Pentagon has and authority to tap into reservoir reserves, but you don't have the money to replenish it. Is there any talk now of just taking that risk and starting to use that $4 billion on the assumption at some point you will get reapplicement dollars since it's looking dire for Ukraine and that the House is not moving on the supplemental? Yeah, thanks, Tony. Well, I certainly don't have anything to announce in terms of taking an approach like that. I think we've been pretty clear as recently as this week when the Secretary was testifying on the Hill to the sask about how critical it is that the supplemental be passed so that we can ensure Ukraine has the volume of security assistance support that it needs in order to continue their fight for freedom against Russia. Well, I need to push back. I mean, you're $800 billion eight organization department here. Is there any discussion though in terms of I think we need to push for this $4 billion? Any signals at all? Any meetings discussing that kind of a plan B? Again, right now the primary emphasis is on working with Congress to get the supplemental passed. That is the most urgent need. That is the most realistic way to ensure that Ukraine has the support that they need for the fight that they're in. So, you know, we're always going to continue to consult closely with Congress and our allies and our partners because again, it's important to remember that it's not just the United States that's supporting Ukraine. This is an international effort. We are committed to working with and supporting Ukraine in their defense. But as of right now, again, we're going to continue to stay focused on getting the supplemental passed. I think a lot of call out when you do that detailed readout, can you discuss whether the F-15 sale that's hung up on the Hill right now was a topic of discussion that Minister Galant pushed for that or if there was any discussion on the need for those planes? Well, take a look at the readout and then we can follow up from there. Thank you very much. Yes, sir. Thank you. I have a couple on Ukraine. We heard Dr. Wolander saying in Congress yesterday that the US was concerned about Ukraine attacking Russian oil refineries because those were civilian targets. Secretary Austin also said that Ukraine is better served in going after tactical and operational targets on the battlefield. At the same time, native officials say that these strikes significantly undermine Russia's economy and its ability to fund the war. So I have two questions here. What is your assessment of the impact these strikes have on the dynamics of Russia's war against Ukraine? And secondly, why does the Pentagon not consider oil refineries that are directly linked to Russia's ability to fund the war as legitimate strategic targets for Ukraine? Yeah, I won't speak for Dr. Wolander and obviously the secretary's words speak for themselves. As Secretary Austin highlighted, our focus is on supporting Ukraine and its ability to defend its sovereign territory. And so when it comes to the situation at hand on the battlefield, we continue to think and support Ukraine's efforts to take back sovereign territory and defend territory from further Russian aggression. I'll just leave it there. Do you have any assessment of the impact these strikes have on the situation of the war? I don't. Yes, sir. Thank you, General. Are you taking precautions against any attacks by Iran or perhaps this? I mean, do you expect attacks on new assets in the region? As I mentioned, again, as we always do and as we've been doing since Hamas's attack on October 7th, we are going to continue to take appropriate steps to ensure the safety of our forces in the region. For operation security and force protection reasons, I won't go into those specifics other than to say the safety and security of our forces is always paramount. And lastly, sir, is the visit of Senkom commander a part of your coordination with Tel Aviv, in case Israel is attacked? I'm sorry. Can you say that again? I mean, the visit of Senkom commander to Israel is a part of the coordination with Tel Aviv. If Israel is attacked? As I understand it, due to recent developments, he moved up his trip to meet with key IDF leadership, discuss the current security threats in the region. But beyond that, I'd refer you to Senkom. Yes, ma'am. Thank you, sir. I wanted to ask about the AUKUS trilateral program and a little bit about the progress. Ms. Zing reported earlier this week that the advanced capabilities industry form would be launched later this month. Can you speak a little bit more about that and kind of what's involved with launching that type of form and what the secretary hopes to see from that part of the AUKUS effort? Thank you. Yeah, sure. I'm going to be infinitely disappointing here and just say that we'll have much more to provide on that in the near future. So just stay tuned and we'll get you more. Let me go to Orin, then I'll go back to the phone here. I think my question was just asked. I was going to ask whether General Kareel's trip was a pre-schedulatory response to the Israeli attack in the West. Yeah, again, my understanding was he had a scheduled trip to Israel, again, due to recent events, moved it up. Thanks. Let me go to Laura Seliman, Politico. Hi, thanks for doing this. Given the Iranian threat to Israel, does the US assess that there is any threat to US forces in the region? And have you taken any specific measures to ramp up force protection? Yeah, thanks, Laura. Again, as I mentioned earlier, from the very beginning of this conflict, two of our key objectives have been to ensure the safety and security of US forces and citizens in the region, as well as supporting Israel's inherent right to self-defense. And so as we monitor potential threats, we're, of course, taking appropriate measures to include any necessary force protection measures. But I won't go into those for OPSEC and force protection reasons. Let me go to Tara, AP. Can I have, if I could ask something? Secondly, since the World Central Kitchen strike, there wasn't the investigation that came out from the IDF. Is the US, as depending on, satisfied with changes that IDF has made to its rules of engagement without talking about specific rules of engagement, but are you satisfied with the changes the IDF has made in terms of the safety of aid workers? Again, as I mentioned earlier, Laura, the investigation that Israel is doing and that the information that they've provided to us is still under review. So again, more to follow as the White House and NSC take the lead on that. Secretary Austin, in his phone call last week with Minister Galant, did have the opportunity to talk about efforts that Israel is taking. Of course, we're going to withhold judgment until we learn more. But we do expect them to take concrete steps to ensure that kind of strike does not happen again. Let me come back in the room. Yes, sir. Thank you, sir. My question is that how important is these two big visits to Washington, Japanese Prime Minister and Philippines president as far as China's threat is growing in the region, including Chinese president said that his goal is to take over Taiwan.  My question is that as far as US national security concerned, so where do we stand? How US will act or react as far as these activities in the region by Chinese threats? Yeah, sure. Well, thank you. As I highlighted at the top, these visits this week are very important because, again, they demonstrate the strengthening of our alliances with two very important allies, Japan and the Philippines. And when it comes to the situation in the Indo-Pacific, it's important, again, to underscore that our focus is on a free and open, secure and stable and prosperous Indo-Pacific and working with like-minded partners to ensure that it stays that way and that the sovereignty of countries is respected and that the international rules-based order is taken into account. And so that's really our focus is on working together to ensure regional security and stability. And if there are countries out there that have a different view that use coercion and aggression, we certainly want to work together to deter and prevent those kinds of activities from impeding or on individual nation sovereignty. Sorry, just to include, where would you fit India in these situations in the region? Because India is also concerned, as far as Chinese activity in the Indian Ocean is concerned. Of course. I mean, as we've talked about before, India is a very important partner of the United States. And the relationship between the US and India continues to grow. And we look very forward to continuing to work with India towards our shared values in the region of a free and open Indo-Pacific. Thanks, sir. I skipped over, Tara, here real quick. Tara, did you have a question or are you good to go? I did. Thank you for remembering me. I wanted to talk to Haiti. What is Pentagon assessing right now with the ground situation in Haiti? And is there any movement of sending additional forces there for any sort of protection? Yeah, thanks, Tara. No announcements to make right now regarding any additional forces, US military forces, to Haiti. Again, as we previously announced, maintaining a small contingent for embassy security at the moment. In terms of the situation on the ground there, you're reading the news just like I am in terms of the impact that gangs are having and the high levels of crime. And, of course, remains a very serious situation in Haiti. Something that our State Department, I know, is following very closely, as are we. But I have no further announcements at this point. Fadi. So since the beginning of the warning, as the Department and the Secretary were very clear that they don't want to see this conflict spread and actions were taken to make sure that doesn't happen, how do you assess the impact of the strike in Damascus on the security in the region? And do you see any risks in this instance by supporting and defending Israel that the US might be sending the wrong message that diplomatic installations are a legitimate target? Yeah, so in terms of the strike in Damascus, I'll let Israel speak for themselves. And when it comes to preventing a wider regional conflict so far, there is not. We certainly hope that doesn't happen. As I mentioned earlier, since the very beginning of the conflict between Israel and Hamas, we have been working very hard to prevent a wider regional conflict from happening. And those efforts continue. Thank you. Yeah, I have a follow-up to what Tony asks. Last night, we know that Russia destroyed one of the biggest power plants near Kiev. And Ukraine said that it was possible partially because they were running out of critical air defense munitions. So is there anything that the US can possibly do alone or maybe together with the help of the Allies to get Ukraine what it needs now, air defense munitions, as we are waiting for the Congress to act? Yeah, and we've been doing it. Certainly, the most important thing we could do is get the supplemental passed. But that doesn't mean that the Department and the US government is not doing anything. As you know, we continue to consult closely with our international allies and partners and with Ukraine on the importance of providing very important capabilities to include air defense to Ukraine. So we'll continue to consult with our coalition around the world to ensure and see what we can get for Ukraine on that front. But again, the most important thing we can do right now from a US national security standpoint is pass the supplemental. All right, thank you very much, everybody. Appreciate it.


Hi Miguel, are you excited to come to Paris the first time, how do you feel about coming to Paris to play? Yeah, it's my first time, really excited. Like I hear so far, it's really nice. I like the area I'm in, it's just dope, a lot of stores and I like how it's built. Just walking around like the town and the city is pretty cool. And yeah, of course excited for tomorrow as well. Just like we adapt when we go across to the west coast trips and everything. We're pros and it's tough obviously, but we can pay a lot of money to be able to adjust. We've been doing it for a while, like I said, going on west coast trips and stuff, but it's not too bad. I mean, when aren't the French national team really good? They're always nice, just a lot of talent.  I know Fournier don't get that many minutes now, but he's like ridiculously good at basketball and it's unbelievable that he's not playing, but it's just sometimes how the NBA is at times, but you got a lot of really good players. Do you think about the Olympics? Yeah, I actually didn't know.  I say that again, I'm sorry. You had some activities with kids yesterday? Yeah. What do you think about the basketball future here in Paris? Oh, dope. It's really good. We actually have it today. We have like the NBA Cares today, so it's going to be dope to see that, but you could tell pretty big basketball fans here.  How's it going, man? How you doing? Just with this kind of extended break in terms of games, one game in eight days, do you view that as a positive after kind of the recent losing stretch where you can regroup or do you really just want to get back out there and get things on the right track? Positive and negative. I think positive is, yeah, you get a little bit more time, a little bit more rest, but I think the negative is thinking about the rest of the schedule and knowing that if we play one game in eight days, you know, it's not like we still don't play 82 games. So, you know, the rest of the schedule will be a little bit more hectic, so that's the negative. And with Viva, now the Olympics, your basketball journey has provided you some international opportunities. Are you able to, like, reflect on that in the moment, or is it hard to, you know, appreciate that while you're in it? For me, personally, it's tough while I'm in it. It's kind of when I'm relaxing and thinking about it and stuff like that. But yeah, like, when I think about the World Cup, obviously it's tough because we didn't win, but thinking about the places I visited, I kind of, you know, reminisced a little bit now and then in the moment when I'm there. For logistics stuff you have to go through. Do you think the NBA game sustained having more games in Europe, for example? I mean, yeah, thanks for sure. Yeah, I think so too. It just has to, you know, I figure out with the schedule. That's the toughest thing, you know what I'm saying? I think maybe if we do come out here, maybe for the future, play more than one game. You know, maybe play Cleveland twice and figure that out besides, but also it's tough because then you got to figure out the home games and stuff like that. So, but yeah, I think if you do come out more, maybe play more than just one game if we're going to be here for a little bit. Was it a good experience? Was it a good innovation? I mean, yeah, it was cool. Obviously, I would probably like to more if we would advance, but it was cool, especially just, you know, everybody's competitive. And, you know, the world, I think, thanks too much about the guys really want the money that bad. It's not really that. It's just we're high class athletes and high class competitors. And everybody wants to win. And so it's like, and Adam knows that and we know that they're just hot. We're just high competitors. So if you put some out there for us to win something, everybody will go hard and try to win. It's just like that competitiveness we have. And it goes longer than just basketball. Everybody I know and play with, they're all competitive in every single thing they do. If it's bowling, if it's miniature golf, if it's any little thing, everybody's so competitive. So that's why I knew it was going to work. Because yeah, you can say the bonus and maybe the world sees it. And it's like, oh, like these guys want this extra 500,000, which is a lot of money. But yeah, that's a benefit for them. But everybody's competitive and wants to have that title of like, yeah, like we won. And you did it. So for the fans, I think beginning of the season, it's a bonus for them. Yeah. Because you have nice activation, right? For sure.  Thank you guys.