Hello, everyone, and welcome to my talk at DEF CON 29. So in this talk, we are going to see the bug hunters record methodology. So before starting, let me introduce myself. So my name is Tussar Verma, and I am working as an application security engineer. I'm also a part of Cinec Red Team and a full-time bug bounty hunter. I'm also an InfoSec trainer and speaker. So let's see the agenda for this talk. So the first thing which we'll be seeing will be the scope review for any bug bounty program. Then we'll be moving forward to before record and after record, like when we are starting, then what kind of information we will be getting from the company which we are testing. And then after record, what kind of information we will be getting. Then we will be moving forward to scope-based record methodology, and we'll be seeing the plus point, the benefit of that methodology. Then we'll be seeing the basic methodology. In this basic methodology, basically, my aim is to just give you an insight like, OK, if we are doing a record. And the main thing is you need to use every single information which you are getting from it and use it to make your record more and more useful for it. You can get more endpoints, more information for it. You can get new variety, and then you can get paid for it. And after that, at last, we'll be seeing the tools and automation frameworks, basically, because nowadays we can automate everything. So we'll be seeing how we can automate these things. And there are many automation frameworks also available in open source. We can use that also. So the first thing is scope review for in-program. So before record also, you need to first do some scope review for the program which you want to start with. So this is a very not-so-easy task for everyone. So you need to first see the assets. So what is the asset for the in-scope and the out-scope items present for any program? Basically, if you've got more in-scope items on your program, then, of course, you can start with it because you have more things to test. You have more endpoints, more in-scope items. So you can start with that. So if the asset is not at you, so you can't, like, you know that in bugman program, everyone is testing on the same program. You have a lot of completion. So for that, you need to be getting assets. Like, if you have more number of assets, the in-scope items are more, then you can go with that program. The second thing you need to say is the number of reports with all. So, of course, like, if anyone is reporting to any bugman program and the number of reports is all is more, means the company is also very active and it is like they are taking action against every report they are getting. And they are patching everything. So, of course, the company is active. So the chances, like, you will be getting a reply from that company is more. So you can go for that company, like, that program also. The third thing, and I think this is the most important thing is the payout, because I think in bug1D, everyone is just, like, hunting for bounty only, like they just want reward, money, huge, like, they are getting everything in bug1D. So this is a very important thing. You need to set the payout, like, OK, for, like, a particular kind of vulnerability, how much they are paying to compare with two, three programs, and the program which you see, OK, this is the best payout in all these three to four programs, and you can go for it. See, it's a personal choice. It depends upon you. Another time to try, then time to bounty. This is a very important thing, like, OK, after your bounty, like, your bug has been accepted, you need to see, like, after how many, like, days you will be getting bounty, how many days it will take to just pay you and all. So you need to see these four things, then only you can just, like, come to a, like, like you can say, we can just make up a mind, like, OK, this program is best for me. OK, we can say that. So then you can start forward and start doing Rekon on that program. So now, for Rekon. So when I just, like, for example, I was, like, let's put in Buckrow or in Hagrid one, we have everything given, like, OK, the, about the company assets, the number of deport is all the payout, and the time to try, then time to bounty. In Buckrow, we have only, like, OK, after these money, they will be giving you a response. OK, so they give everything, like, clearly, it's mentioned everywhere. So you cannot say it from these two. Now, after that, when you will be jumping into that program, you will see some basic information which is available for every program. The first thing is company name, of course, let's put it in the scale of company name X, Y, Z, and you will be having the available scope also. So, like, all the in-scope items, out-of-scope, this thing will be given. They will be also giving you some overview of the company business. And the fourth thing will be, like, they will give you some out-of-scope identity, like, they don't want these bugs to be reported. And they will also give you some focus area, like, OK, focus on these bugs, these endpoints, because they want that endpoints or that one to be tested on their application. So these are things which is given to you before Rekon, like, you're getting before Rekon only. Now, after doing Rekon, what things you are getting? So, after Rekon, we are getting, the first thing is the service info. The second is the backend technology use. The third is the interesting endpoints. The fourth is the juicy links, which may be vulnerable. And then we are getting more and more things, like, after you're doing Rekon. So, of course, you're getting more and more. So these are things, like, before Rekon and after Rekon, you're getting. So now, the main thing is, like, how to start doing Rekon. So the scope-based Rekon methodology by Harfotra is the best one. Why? Because the first thing is, like, it will be saving you a lot of time, because you know, like, OK, for that particular scope, you need to test that things only, like a limited number of things only. You won't be, like, mixing up everything. OK, the first thing. The second advantage is, like, the chances for getting duplicate or autoscope bug will be very less, because you know about your scope, right? So if you know about your scope, then, of course, it's a very good thing. And the chances of getting a bug, which is not, like, accepted by company, will be very less, so it's a very good thing. Also, you can automate your Rekon workflow, because you know about, like, OK, the scope is, like, small or medium or large. So, of course, you can automate that workflow also. And then you can just get all the information in just one automation. And it will also, like, you know, basically, the thing is, like, just blindly doing Rekon is not a very, like, not give you anything, OK? So you need to understand the workflow first. So for that, scope-based Rekon is the best thing. So, if scope-based Rekon, basically, we have three types of scope available, the small scope, the medium scope, and the large scope. So the small scope, if you are getting, then you'll only get a single URL, like the domain or the subdomain, OK? So if you get any, like, for example, evu.com or info.evu.com, then, of course, it's a small scope target. We'll be, like, moving forward with a small scope Rekon. The second one is the medium scope target. So in that, we'll be getting a wildcard domain, that is star evu.com. This is a, like, you can just see, and, OK, if there's a wildcard domain present, then, of course, you can go for the medium scope Rekon. Then comes the large scope one. So anything, like, if you are testing a company, so anything about the company, which is related to that company, we will be in scope, so you can do a large scope Rekon on that company. Now comes the basic methodology. So, like, why, like, just, for example, if we are starting the Rekon field, OK? And we need to, like, we are getting a target, let's evu.com, it's just, like, medium scope one. So we need to start a Rekon here. Now the main thing is what happens in Rekon, basically, we just go on blindly doing Rekon and we don't use every single information which we are getting from it. So I will be giving you a basic, like, like workflow, like, what we can follow, and then you can automate also with some tools. So for example, if we get our target, let's evu.com, it's a wildcard domain. So we can first start doing the, like, we can run a subfinder, MRs, and we can get all the subdomains. And we can save it in a folder, let's say the, any name we can give it. Now we have got all the, like, after getting everything from that, then we can just move it to the HTTPX or HTTP Pro, and we can fit out the active endpoints from them. Now after getting the active one, we will be making one more folder for it. Now we got two. Now let's support that we need to get more and more information from these two only. So we'll be carrying out the active TXT file, and we will be, like, moving, just making it a scan from the, like, we need to get some more endpoints, some URLs from it. So we'll be using Wayback URL and Go, and we can get all the, like, endpoints which can be, like, we can just go on for testing also and any input which related to that particular domain we'll be getting from that. So now we got three files saved. Now after that, we can, now we got the first file which is having only subdomains. So now what we can do, we can just use the pub tool and we can just, like, get some more endpoints. We can put four of them, and if we are getting any, like, response for, like, four access, we can try to bypass that. So now after that, we'll be getting one more file, we can just save that file also. Now we got four files, just keep in mind that. Now after that, we can do a NMAPS and all the active TXT file. And in that, and, like, after doing that, we'll be seeing all the open ports and everything available. So we can now save it as a, let's say, we can save it one new file now again. So we got around, like, the first file which is having only the subdomains. The second file is having only the active subdomains. The third file is having the data which we got after using first. Like, we are, then the fourth one will be, like, having all the endpoints which we got from Gov and Wayback URL. And the fifth one will be, we are getting all the open ports from NMAPS. Now the main task is to get some endpoint which we can start testing for the SQL or let's say, XSS or any other vulnerabilities. So for that, we can use GF or GF pattern. And then we can start, like, just, like for example, if you want to test for XSS, we can just use GF pattern and get all the endpoints which can be, like, can be vulnerable to this, this particular bug, OK, like, or XSS or SQLI or LFA or anything else. So we'll be getting that. We can save it in a file. Now if we want to grab some JS file also, we can do that also from that. So these are some things. Now after collecting every file, now we can just use an automated scanner also and we can pass all these files and we can get, like, some variety from them also. Like, we can just get some more endpoints. We can get some variety. We can get some more information on what target also. So this is a flow, like, we are using every single information which we are getting from Rekon, we're not wasting it, OK. So now this is a very long work, like, of course, I'm not telling, also, now I am, sometimes I'm mixing many things. So it's a very long, like, process and it will take time doing manually. So you need to, like, automate everything. So nowadays, in open source, we are, like, we have got various, like, tools and frameworks which are available. So the best one, like, which I am also using, the first one is the Rekon FTW. Rekon FTW is, like, it has everything, like, automated. Everything, like, every single thing which you want to do in Rekon is, like, put it in this tool and it's a free open source tool. So you can use this to automate your Rekon workflow. The second one is the Project Beam by Hertz Botra and this is a, like, it is working on the method of scope-based Rekon. So if you're following a scope-based Rekon methodology, then you can use this tool. The third one is the Osmedius. It's an old one, but now also if you are, like, if you want to just do a Rekon scan and all, then you can use this tool because it is also giving you a proper result of that. Of course, it is, like, because these three tools are doing a lot of Rekon work, so it will take time, of course. So if you don't have, like, a higher internet connection, then it will be very, it will take time. And of course, like, because the tools are doing many videos, same. So you can do one thing. You can just, like, use this tool in background and do things manually also. So manual plus automation, if you're doing in Rekon, then, of course, it will be very, like, it will be giving you an advantage also. And the main thing is, because you know, like, what you're doing, because if you don't understand the workflow about these tools and all, then, of course, it is very, like, hard for anyone to, because you're just, like, for example, you're getting every information, but you don't know how to use that information further on for your testing. Then it's a waste of time for you. And, like, if you're running a tool, you're getting many various information, but you don't know how to use that. So, of course, it's a waste of time. So don't do that. Always first understand what you want to do, what you want from the target, what kind of information you need, and then only start your Rekon. That's all. I hope you, like, enjoyed my talk. If you have any theory, then you can contact me on these handles. Thank you.


Santa knows where to find all the best and hottest smartphones just in time to make this Christmas better and bigger than ever. Better service, bigger savings, that's today's Appalachian Wireless. A 95-year-old woman was the talk of the town this morning as she was picked up by Floyd County Sheriff's Deputies in a police cruiser and taken to the Sheriff's Department. One may think, what on earth could this sweet woman do to get taken in by police? Today, Gertrude Tyson wasn't brought in for crime, it was to celebrate her birthday. Birthday to you, happy birthday, sister Tyson, happy birthday to you. Check on a senior today was implemented by the Floyd County Sheriff's Office roughly eight months ago. The coast program allows a volunteer with the Sheriff's Office to call to check on elderly residents who don't have family in the area. If the senior doesn't answer two consecutive phone calls, the Sheriff's Department will send someone to check on them. I'm a senior citizen too, and I've been retired for quite a while. It gets me out of the house. These senior citizens that I call, they'll say, your call is the only call that we get during the day, and we wait for you to call. Sister Tyson is the oldest senior participating in the coast program in Floyd County. We just got to thinking, if they don't have anybody calling, checking on them, if they don't have anybody maybe going by and checking on them, they ain't going to be really celebrating a birthday or a special occasion. During today's surprise party, cake, refreshments, and presents were shared with Sister Tyson. I love all of you. In Preston's Burg, Shelby Porter, EKB News.


We begin the stories with breaking news as there is a case of the two state house of assembly as seven members of the house have announced the impeachment of the speaker. The seven all members of the APC gathered early this morning to sit and relieve the speaker of his position, but the PDP lawmakers are protesting. They consider the impeachment illegal. That's because it's constitutionally takes no fewer than a third of the legislative house to impeach a speaker. There are 24 members in the platoon state house of assembly. The minority weep of the house joins us on phone. Good morning. It's good to have you join us this morning. And very well. Thank you. Can you describe what is happening right now in platoon state as regards the assembly gathering? Before we were at home when we were told that since the seven members of the platoon state house of assembly, they walked in this morning around six and they arrived in the chamber to impeach the speaker. And we were about to enter too. Why they asked a security man to stop us? We only managed to enter the house around 8.30. And when we did, we discovered they have done that immigality. And therefore the constitution of the federal public of Nigeria is clear. It is only to talk of the member that we impeached the speaker. And by calculation, we have a 24 member. It is expected that only 15 members have the right to impeach the speaker. Now what is happening now? We are very certain that that will not stop in the face of the meeting. We will not allow something to happen. The member of the PDT are very resolute behind Mr. Speaker. And we have other people, people in the ATC that are not in support of other people. So we have the majority. But there is no way, there is no way that Mr. Grono will use security data in the data house. We will not allow something to happen. So we are right here waiting for our speaker to come. So we will deliver it. And in the middle of the house, the people go free. I want to assure you that we are going to suspend them. We will suspend them, suspend them, the determination of the committee that we are going to set. I am pretty sure that Mr. Speaker will not allow something. So we are waiting for Mr. Speaker to come. And I thought that our speaker will remain honorable. I knew her book. I thought that the people are our speaker. So that's your statement. All right. But why do we have the PDP members opposed to these? Because apart from the fact that the constitutionality of this action is questioned, it's an APC member that has been impeached at this point in time, APC impeaching an APC speaker. What we are saying here is very simple. You see the PDP member outside but if we don't go for legalities, we want the right thing to be done at the right time. That is our start. So what we are saying now is this. You see, there's no way, there's no way, any member will come and impeach a speaker. There's no way that will happen. No, Mr. Godno has his own right as the executive governor to do what he wants to do. But he has no right to intervene in our business. We have our autonomy. So we have the right to do things. It is not him to bring security and take the data. If you are here in the Patristeras or assembly, you will see what is happening right under it. More than a thousand slip-in men are here. And that will not stop us from doing our function. All right. Thanks so much for making that time to speak with us at this point in time. We do appreciate it and we hope that things actually pan out well.


Rich Pigs Daily is an online community for traders to exchange smart, straightforward and profitable investment ideas. Join us today at richpigsdaily.com. Subscribe to us on YouTube to learn useful stock trading secrets and discover the next ten-banker. Hi, guys. How you doing? This is Rich from Rich to Be Live and today I want to speak to you about vicinity motors corp, otherwise known as BUSXD in America and VMC in Canada. So first, we're going to go through the American chart. You can see that it's been as low as 54 cents. Obviously, it did a reverse three to one. So a little bit of this is that, but you can see that this trend has been clearly going up and this has been a very big success story already for our community and I believe that this is a company that's just getting started. Now what's happening in the electric vehicle sector is that most electric vehicle plays have retraced and come back from the excitement that they had earlier in the year when they were just on fire. You can see right here, vicinity motors been on a tear come all the way up from under a dollar to where it is today at 742. It did have a nice run up all the way to 1290 was the high, as you can see, when as high as 1290. That was the trend all the way up there and has since retraced to where it is right now at 745. Now I believe that this is actually a very good buy zone for BUSXD. Now in saying that, just remember Rich to Be Live is strictly for education and information purposes. But if I draw this trend line here, since they've done the reverse, this is pretty much the lowest it's traded. It's kind of in the low zone and this is a company that is growing in revenues, has a really super tight float of only 29 million shares. And with all the business they are doing their revenues, this is a company that will be EBITDA positive and also making the application to the NASDAQ. So there's a lot of catalysts coming here for BUS, VMC vicinity motors corp. Now the other reason why I think this is close to the buy zone is you can see here on the RSI that they are literally in the buy zone currently at 37. Anything 30 or under is a screaming buy. It is approaching that buy zone right now at 37, 37. So the RSI is signaling a buy. You can see the trend line is up. So this trend line could continue based on this trend line. We could see this continue further. And I believe it will continue further up. So as an investor, you're always looking for a trend. You can see the trend line is up. So I believe that this will continue up and this retrace is nothing short of a buying opportunity. And if you look at the MAGD, you can see they did cross up, which was very bullish. It has now since come back down. So many different reasons why I believe vicinity motor corp is a buy. Now, if you like this video, please smash the like button, comment down below, share the video everywhere and subscribe. Like I said, almost all electric vehicle plays have given back earlier gains and retraced vicinity motors corp is doing similar to everything in the industry. But this is a company that already has sales. They are on pace to do 25 million a quarter, which would be about $100 million in 2021. So lots of real revenue and real sales for vicinity motors corp. And we've seen them go as high as 1280. We're right now at 740. So if you were to get in at this $7 range and for it to go back to $12, you'd be able to make a nice return on your investment. If this went back to 14 or this went to 14 or 15, you'd be able to double your money on vicinity motor corp. And because it has such a tight float of only 29 million shares, it's only going to need one big news, one big catalyst and some revenue growth and some more big orders to potentially make this bust and explode. So love to know what you guys think. If you agree with me, please comment down below on this video. Remember, we are strictly for information education purposes. Consult your financial advisor before you invest in anything that we talk about here in rich to be live. Always invest in the best. The best is blessed. We love to bring you early stage rockets. We brought you bus first. We brought you VMC first, BUSXD first. And it's been a big winner for the community. And in my opinion, they're just in the first inning. Like I said, many catalyst to come NASDAQ list incoming potentially more revenues and EBITDA positive company priced right to explode. These are more rich from rich to be live. If you're not winning, you're not watching. We bring in the winners and we bring them to first. What do you think of this video? Do you agree with me? Do you disagree with me? Comment down below, share the video everywhere and subscribe. If you're alive, hit that bell for notifications. So every time we have any big breaking news, you'll know first is your boy rich from rich to be live. And if you guys haven't joined our club, go to www.richpigsdaily.com where you can learn to trade stocks and cryptocurrencies. Join the club. It's your boy rich from rich to be live and I'm out. Peace. It's just about time for the money bus to yield big, big, big returns. I feel like it's coming. I can feel it in my bones. What do you guys think? I'm out. Peace.


Hello, I'm here today to talk about what's going to happen on April 1st, 2022, when the National Archives releases the manuscripts forms from the 1950 census. What we'll see on April 1st, 2022 are the handwritten sheets that are a portfolio size filled out by 144,000 enumerators, the field staff for the 1950 census, as they fanned out across the country on April 1st, 1950. When they were done, they had visited about 46 million houses and homes across the country, reporters, special places, and had counted and reported information on some 150 million people. The enumerators had maps, supplies, as they call them, and instructions, almost all of it on paper. They had been hired and trained in the previous month or so. They were to go house to house to collect the information from their assigned local area, which was called an enumeration district. It was a very temporary job. It was basically all over for the enumerators and the field staff by September of 1950. By then, the paper portfolios had been checked, edited, bound, and shipped from a local census field office around the country to either a processing office in Philadelphia or the main census office in Suitland, Maryland. The portfolios were delivered to the keypunchers, who transformed the information on each person onto a paper punch card, one for each person in the country, so about 150 million of them. The process started in August 1950. It took till July of 1951 to punch them all. The population form in the portfolios that the enumerators had used had space for about 30 people to be listed. The forms were big, 19 inches by 22 inches. From the perspective of the Census Bureau, the people who were going to compile and tabulate and publish the information, the handwritten responses on the main schedules, the main census forms, were simply designed for the fieldwork. Tabulation work and publication took place once the information on the handwritten forms was transferred to the punch cards. So after the punching was done, all those paper forms were microfilmed and put away for reference. The bureau and the archives preserved those microfilms, but they destroyed the paper versions in the 1960s. So what we're going to get on April 1st is the microfilm of those paper copies that was made in the early 1950s. And now it will be up to the genealogists, the historians, and the public to explore once again the handwritten reports of those 144,000 enumerators with the names, with the addresses, and we will see the very ordinary record of what happened when the census taker came calling in the spring of 1950. Thank you.


This study found that Entipro BNP has a high sensitivity for detecting pulmonary artery hypertension, PAH, but its low specificity makes it difficult to use alone. The authors suggest further validation studies and combination tests to improve specificity. This article was authored by Achesian-Smiths, Lisa Boitros, Marij K. E. Moll and others.


Okay, so here is the aseptical unit that I have, and I do have two handspeed hookups for it. But I'm going to show you how to get your slow speed to work on the aseptic. So for starters, what a lot of people don't think is make sure on the bottom. This is towards the F. Sorry, I can't get it to focus right now, but F and not R. If it's towards the R, then quite often your, your proficup won't spin. So make sure this little, I guess, toggle or whatever you want to call it is towards the F. Okay, so I'm going to put that back. This is how I have it for the slow speed handpiece. So if you look on the side units here, you'll see, sorry, all the cords here, you'll see handpiece, there's one on this side, but I also have one on the other side as well because I have a slow speed and a high speed hookup. This one is for the slow speed, depending on what system you have, it might be on either side, but on and off. So the switch is towards on this one here, it's towards low. Since I'm using a low speed or a slow speed handpiece, if it was turned this way, your, your, your slow speed wouldn't work. So you need to make sure that's for low if you have this function and make sure this is pushed on, but you also might have to play with this one down here. If the motor's working, but nothing spinning, you might have to adjust both of these. Okay, so see how there's different toggles again. You might have to adjust this one. So I suggest playing with it and really try, but then if you notice I have another one for high speed. I don't want the high speed, so that's why I haven't really played with this one too much. Sorry, that would be this one here. So you might have to play with a couple things, but the main thing is make sure this is switched to low.  So I hope that helps. I have lots of different hookups here, but that is specific to the slow speed. Good luck and let me know if any questions.


So, I know that lately the news cycle has been incredibly depressing, but I saw something that put a big dumb smile on my face and I thought that I would share this with you because I think that you also will find it as entertaining as I did.  Take a look. Love it. Just it warms my heart so much. That person who yelled that is an American hero. That person is a true patriot. So if you're watching this, sir, I hope that you know that we appreciate you. We value your service. Now, we are going to take a look at it one more time. This time when you watch it, pay close attention to the guy on the right. He's on Ted Cruz's left because his reaction is hilarious. God bless you. The virus, the evidence is overwhelming. I think escaped from. Love it. Love it.  Now, this video got me thinking. So in the event I were in public, would I also yell something at Ted Cruz? And I've thought long and hard about this actually. And I have concluded the answer is absolutely. I think that in the moment, if I saw him in public, the adrenaline would kick in and I feel the need to do something. And of course, I wouldn't walk up to him and Haka Lugi in his face or something. That's what he deserves, but I wouldn't do that, but I would yell something. The question is, what would I yell?   But what do you say? And I think that just saying Ted Cruz sucks, that is, it does the trick, right? But I would want to do something more mean in my opinion.  I'm not sure. That's the thing that really has me a little bit, I guess, perplexed by this. I want to yell at Ted Cruz if I ever saw him in public, which I would not. I wouldn't get the chance to do that. But if I did, what would I yell? And that's really what has me drift up and I don't know what I would yell.  Like you want it to back a punch. So what do you say? So I am going to outsource this question to you all because I know after watching this video, you're thinking about this too. What would you yell at Ted Cruz in the event you saw him in public? It's a tough question because there's so many options. I mean, you could critique him for eating a booger on national television in 2016. You can criticize him for being smarmy and fake. You can call him a sellout. You can call him a beta male because Donald Trump called his wife ugly. There's so much, but you'd only have a fraction of a second to get the point across. So what would you say? And honestly, as I think through and as I have been thinking through what I would say, I felt something that I haven't felt in a while and that is happiness. So, you know, I initially kind of hesitated to talk about this because it's not substantive, but when the news cycle is so dark and when I genuinely feel depressed and bogged down by everything that's happening in the world and in the United States, we need to celebrate moments like this, moments where we all feel just genuine happiness from. And I think that everyone in America can agree that Ted Cruz is one of the biggest pieces of shits in the country. So seeing somebody yell at him, it just. Do I say it's wholesome, even? So, yeah, I don't know what I would yell at him.  I just feel like that wouldn't suffice. It has to be much better. So let me know what what you would say to him, but you would yell at him. And I hope that this video put a smile on your face as much as it did mine because this certainly brightened up my day. That's where we're at, where we're trying to extract joy from videos where people yell at Ted Cruz. But hey, when you're living in a late stage capitalist dystopian hellscape, it's the little things that count. And this certainly counted. Thank you so much to that person who yelled this at Ted Cruz.


Hey there friends, how's it going? My name is Kevin and today we're playing Far Cry. It's a Far Cry from an original idea. No, I'm not going to go down that route again. We've already tried that and Far Cry jokes are not funny. If anything, they're offensive. This just turned into an apology video. I'm so sorry. I find it so funny because this game is so old and their artwork is just Far Cry and just some regular font and some weirdly cropped screenshot and also I just downloaded the game and this little image of the main character comes up and it's like Far Cry's finished downloading. I'm ready.  Why is that the game's little image? Carps stay in seconds off. Put that way up. I want them all littering the map. Current profile default. Yeah, sure. Default is on the island. What is AI Auto Balance? You're going to have to be more specific. I don't know what this does. Does this mean the teams with Auto Balance and some of the enemies will come on my side? Oh my god, the intro. It's like living across the street from a nightclub at 2am. Okay, she's going off jet skiing for some reason. What? Where did that come from? We were out in the middle of the sea.  Oh, he is pissed. He financed that boat. He still owes a lot of money on that. Just to clarify, this is still the intro. It's so overwhelming. There's monsters everywhere. There was a volcano a second ago. He's just down there motionless in the pit. Okay. Is that wild intro finally over? Can I just play now? I'm so confused. Okay. Strange in itself. Everything in this game is strange. Oh, sweet Jesus. He must have fallen down the stairs. Okay, be very careful. That happening to me. I've got to find a way out of here. I don't know that voice for some reason. It just makes me laugh. It's like the most generic voice ever. Oh god, another victim. He fell down a ladder. Right, be very careful. Very careful. He's a bit drunk. Listen, dirtbag, keep an eye out for some punk in a red Hawaiian shirt. If you see him, call me at once. Am I understood? Yes. Yes, sir. I'm heading out. What was that? Oh, you sure showed him. He's looking right at me and he can't see me. There's someone over there. What was that? He just dislocated both his arms trying to grab his gun. I don't even want to advance. I want to go back. Oh no, the whole place has collapsed. I was just going to say I want to see what he's up to. What's the use button? Please tell me what the use button is. It's not that. Let's throw rock.  All right, I cannot figure this out. Hold on. Do we have controls? Use is F. I've been pressing F. Oh, I lied. Okay. I guess the text has to be on. Hello. Oh, look, this must be the future of video on phone. Impossible. How do I know I can trust you? I love everything about the main character Jack in this game. Like his voice is so generic. His look is so generic. He's got like tribal tattoos that look like he went into the tattoo parlour and just opened the tattoo book and went first one. That's it. That's the one for me. Oh, there's enemies here. I'm not too concerned. Like that one's fishing. He's playing Stardew Valley. Well, he was playing Stardew Valley, but the way the other guy behaved earlier, I'm not too intimidated by the enemies. Oh God, I'm looking for a weapon. Okay, I got a machete. I'm practicing. Come on in. Okay, I think that's all of them dealt with. I'm like a shark. I sensed blood in the water. Oh, did you hear that? He just took a big slurp of it went. He quenched his thirst for blood. I don't like that song. I'm just out here bird watching. May as well make the most of my time on the island. No, it was like hitting concrete. It's on the other side of the island from there. What's wrong with him?  Who reacts to drowning by going, Oh, under the water. Hello. I don't think anyone noticed somehow. I'm out here hunting the greatest game of all.  I'm glad I turned off the AI balancing thing. I don't want them on my team. Oh, how about that explosion? Oh, the alarm's going off this way. How are you dead? What? How are they shooting me? Okay, I lied. I want some of them on my team. I didn't realize they had X-ray vision. Unfortunately, that guy had no vision at all. He just walked in and looked at me, did nothing. Can I drive vehicle? I can. Oh, sweet Jesus. All right, it doesn't matter. We can drive out of this, I'm sure.  Oh, God, damn it. Oh, well, easy come easy go. But now I'm out in the middle of this desert. Oh, wait, hold on. Is that a mirage? This is the dead guy next to a car. Okay, I guess you won't be needing this. Oh, that's the wrong way. That is up. I don't want to go up. I need to go around the mountain to get where I need to go. I don't know where the hell I'm going. Oh, into water again. That's where I'm going. Back it up, back it up. Can he honestly not hear me? All right, I guess not. Guys, watch out. I'm lost. Please get out of the way. Oh, God, I stomped both of them. Like, I'm just committing various crimes on this island. I don't even know if these are bad guys. I open fire first. All I know is I'm having a blast. You know what they say, don't do the crime if it's not fun, but these are very fun crimes. Oh, this is where I'm meant to be in the ocean. Did I just hear a snake? I'm underwater. The fish ratted me out. Did you hear that? Damn it, I'm sealed in. What? I'm very confused. I was in the ocean, then it just teleported me here, and now I'm sealed in. I don't understand.  Oh, little hole. Reminds me of Harry Potter just jumping into every hole he sees without knowing if there's a way out at the other side. What? Where? Oh, there you are. Also, what do you mean? It's you. I don't believe we've met. What? Oh my God. There's been so many instances where I've been attacked, and they've not even gotten close to hitting me. I've just been walking through their bases. Nothing happened, and that guy just one shot me. Yeah, like, how come these guys can't hurt me? Oh, no, he raised his left. I love how he got blasted across the room, and the other guy's like, are you okay? Wait, is it through here? Okay, I got completely lost for so long. Oh God, there's someone here. No, don't hang out your binoculars. Honestly, if you need binoculars to read what's right in front of you, you might just consider glasses. It's a bit more practical. That was completely unnecessary.   Honestly, it was a mercy kill. You don't deserve to be living in this hell.  Maybe you'll get respawned in a different game, a more modern game, like Tetris. Any sign of Al? No, not unless she was cleverly disguised as a mercenary intent on killing me. God, what is with the attitude, Mr. Generic? Come on, he's trying to help you. You see that? See what? I'm going to get closer and figure this whole thing out. Oh wait, no army music is starting. Now they've actually seen me.  Maybe going down to the deck and just being immediately spotted isn't a good plan. Jesus, what was that? Oh, it was him. I thought it might have just been the wind.  We're under full attack here. Oh my God. What? Okay, I found another video phone. Got his video phones way cooler than my video phone. They're all going to make fun of me if they see my video phone. I love that in older games when you pick up health packs. What were you guys even doing in here? There's nothing in here.  Oh my God, there's tons of them everywhere. Oh my God, what is going on? Jesus. How are you supposed to pass that? I don't even know who's shooting me. It definitely wasn't that guy anyway, because he didn't even react to me. No, I don't want to right now. At least he chose insult instead of fighting. He lowered my defense instead of actually doing damage.  I got shot through a box or something. Okay, you know what? I'll just kill myself for you because that did not go well. What are they looking for? Wait, what? Oh, he said I'm blind. Okay. It helped that he shouted out exactly the effect he was under from that grenade to really consider it, to be honest, these enemies. Oh sweet, but Jesus, this bridge is not very reliable.  Oh my God. Wait, that did nothing. Okay. I was like, that's cool, but it didn't actually accomplish anything because it just lowers a foot. Oh, now that is cool.  Jesus Christ. I'm using the F key to push the boat in the water, but it's just kind of flailing all over the place. Oh God, I'm going to break something here. Oh no, no, no, no, hold on.  All right, hold on. I can do this. I hit the boat a lot more than the chain. It's smoking and I need it. There we go. Perfect. It's in a horrible state, but it's mine. No, you know what? I disagree with that idea. I'm just going to head out to open waters and keep going until I find land. Who knows? I could be the next great explorer who discovers a new land. In fact, I think I've just discovered Bikini Bottom. Look at that. There's just nothing. Wait, what? What? What hurt me? I just started going out to sea. There we go. I've marooned myself instead. I like this. Just me, the island, and rum. Oh no, where is the rum gone? Oh, and the coconuts are fake and everything. All right. Well, this is my life now. Oh wait, no, I'm dying from island madness, I guess. Yep, I'm dead again. What do you go out of bounds? The game's just like, no explanation, just you are dead. Well, if I'm dead, I guess that's the end of that. The game and me are going to have to agree to disagree. It wants me to keep playing, and I don't. I want to go out to open waters, so it doesn't want me doing that. So I guess we'll end it there. This was a blast from the past. I don't remember this game being this goofy. It was fantastic. I love the way he took out that gun. All right, but we're going to end it there. I hope you enjoyed this blast from the past. And if you want to watch more of me, I post every day, and I also stream over on Twitch four days a week if you want to check that out. Link is in the description. But for now, I'll just say thanks for watching. I appreciate you as always, and I hope to see you next time. Bye for now.


Ladies and gentlemen, it is a pleasure to join you virtually on the sidelines of the first India G20 Development Working Group meeting. In my role as the United Nations Secretary's Special Advocate for Inclusive Finance for Development, I will work closely with partners to ensure that financial inclusion was recognized and embedded in the Sustainable Development Goals. Why? Because financial inclusion is a powerful tool of development. Eight of the 17 SDGs highlight financial inclusion as a way to help achieve zero poverty, no hunger, good health, gender equality and economic growth. We know financial inclusion can do this, and we have the data to show it. Our main source of data is a global financial inclusion database, the Global Fintechs, as we call it. We follow the Fintechs, which does not have reliable information to answer vital strategic questions even the number of people we hope to reach. After the first edition was released 10 years ago, a picture of financial inclusion emerged that transformed global thinking, planning and action. Today, countries around the world have high quality data on how adults are saving, borrowing, making payments and managing risks. The big picture is that 71% of adults in developing economies now have a formal financial account. A decade ago it was just 42%. The data helps provide a close-up view. We have learned that when rural households in Uganda started using mobile money accounts, the food security increased by 45%. This year's Fintechs report covers new ground and offers fresh insights. For example, how financial worrying and resilience affect the way people manage shocks like job loss, illness, crop failures or natural disasters. How is this new data being used? Often to create better financial policies, products and services. We can see this with businesses that serve the poor and vulnerable. In October I visited Tanzania and met with small-whole of farmers who now have the protection against the impacts of extreme weather. Acre Africa offers micro-insurance and affordable digital weather index insurance product. Weather satellite data makes it possible for Acre to assess and predict risks as well as trigger payouts when disaster strikes. Local financial services are then used to send payments to farmers quickly, safely and easily. The confidence farmers feel from insurance coverage has helped them seize new opportunities. They are now investing in better, drought-resistant seeds and using inputs such as fertilizer to boost their crop yields. The better the data, the bigger the impact on people's lives. However, a lot of data remains siloed within companies or government agencies, essentially as stranded acid. Accessing one's data is another challenge. For most people, it is nearly impossible to share their own data and use it to select suitable financial products or get better terms such as low interest rates. When individuals or businesses do share their data, they often do not know how it will be used. Most common consent without reading the terms and conditions, which as we all know are often long and hard to comprehend. In short, people are not benefiting from their own data. They deserve more transparency and involvement in how their data is collected, shared and used. The EU Data Act and India's data empowerment and protection architecture could offer some examples and insights into how trusted data sharing can protect and empower individuals and small businesses. During today's side event, you will be able to discuss these important issues. So let us ask, how can we use data to fast-track progress on the sustainable development goals? How can we share and learn about different approaches to data governance to figure out what might work best in our countries? And how can the public and private sector work together to use data and AI tools to support development outcomes? I look forward to following your discussion and the progress of the working group over the coming year. Thank you very much.


Instincts part two, I know we already talked about instincts in one of the other videos, but it's such a, you know, it's something that I kind of want to drill home, and so I decided to do a second video on it, but, you know, at the end of the day, like you have to know, you have to know your why, you have to know why you do what you do, you have to go with your inner convictions.  However, everybody has their own path to walk, everyone has their own journey, everyone has their own process that's unique to them, and I truly believe that, like, you know, digging down deep and going with your inner convictions, like, that will really help you along the way. I remember when we first started, when I first started a company with CPG brands, when you're manufacturing pretty much anything really, food, clothes, you have two options.  But again, that's why I'm saying, like, you have to kind of know why you're doing what you're doing. And so, when we first started, yeah, I was making the product by hand, and then as we were starting to grow and pick up traction, we realized, okay, we're going to need to either get machinery or use a co-packer, and so I did do one round with a co-packer, and that first round, that first order went pretty smooth, but as I'm in the co-packer's facility, I'm walking around, I'm looking around things, and I'm like, I can, because my background is culinary, and so I'm like, naturally, I can do this, like, I can get some equipment, I don't know how I'm going to afford it, but, you know, we'll just make it by hand until we figure that piece out.  I just felt like I was supposed to step out and build our own plant. I'm like, I want to, you know, have my own team that I get to call family, et cetera, et cetera, regardless of the struggles that come with it. So that's what I decided to do. We opened up our own plant. We started little by little, moving forward, moving forward, building one step at a time, and we ended up, and to this day, like, I don't know what the next five years or the next 10 years are going to hold. But as of now, like, I think that's probably one of the best decisions that we made. One of the things that happened, one thing that I realized later, just hearing stories from other people is when, because, because co-packers, what they're doing is they're making product for hundreds of other companies.  And it becomes this political game. I didn't know that at the time, but as I'm hearing stories from peers in the industry that are working with co-packers, it kind of proves my point. COVID-19 hits, you know, a couple years ago. And what did that do to the supply chain industry? Everybody, co-packers were stressed. Co-packers had more business than they could actually handle. And so it, that's why, you know, and I don't know if you guys are doing shopping or your families, but that's why you would go to the stores. And there was nothing on the shelves because people couldn't produce quick enough. Because we were able to handle our own production. We never had any shortages. We never had any out of stocks. We struggled to get a couple of ingredients in there. But we were in charge. We were in control of the full production process, which was my inner conviction when I made the decision to double down on self-manufacturing. And so this whole thing wasn't about me being right, because there's a lot of challenges that I deal with where I'm like, I hate fixing things. And this guy right here, that's the culinary guy.  But it's for a greater good. And so this is more so me saying, hey, I had the, I could have listened to what folks were saying, but I, there was just something about that inner conviction. There was something about that, that prompting. And I went with it. And so far, it's, it's doing good. So again, go with your gut. You know, a lot of times it'll stare you in the right place.


All right, thanks everyone for coming quick introductions. My name is Alice and I am an emissary ingress maintainer I'm Flynn. I'm also an emissary ingress maintainer, but I do not work for ambassador labs anymore. I'm now at buoyant Just in case anybody was wondering why I'm wearing the linkerd t-shirt Cool, so just to get started. I'm gonna set the agenda We're basically just gonna go over some intro about emissary ingress some recap about what we have worked on Get into a bit about how you configure emissary ingress. What are the benefits and stuff about why we chose the way we did to configure it? Talk a little bit about the 3.x major version. We released since the last cubecon Talk a bit about the path to the next version of CRDs and Then lastly mention a bit about convoy gateway. What's been going on with that and what our plans for the future are So to get started what is emissary ingress? Well, it is an API gateway So you've got your back-end services that are sitting in your kubernetes cluster You've got your users that are sitting outside the cluster and you've got emissary Which is the main gateway the front door into the cluster all that traffic is gonna be going through emissary from Externally into the back-end services. So that is the primary thing that your end users are going to be communicating with Emissary basically consolidates all of the things you want an API gateway to do into a single control point So a bit more detail on what it looks like in the cluster So as a background emissary focuses primarily on providing a self-service developer centric experience for controlling the gateway Emissary is powered by convoy proxy. So emissary is going to be sitting in your cluster It's going to be listening and watching for resource updates, and then it is going to be spinning up and configuring an convoy proxy So outside traffic is going to be talking indirectly with that convoy proxy that is managed and configured by emissary And that's going to get the traffic to your back-end services Like I mentioned emissary is an API gateway, but it is not just a proxy Emissary ingress also does authentication and as well as lots of other cool control patterns for traffic So let's say we've got two users here We've got Jane and we've got mark and they both want to access the service You can inspect things that are more than just the path things like the HTTP header All sorts of different things and say like hey Jane is going to go to this service and mark is going to go to this other service We also support extensions for authentication So let's say Jane wants to update some thing on the application and mark does too We're going to talk to that extension for authentication first We're going to say okay Jane is allowed to perform that update, but mark gets banished to the shadow realm So beyond authentication we've also got extensions for observability things like tracing rate limiting and resilience patterns A lot of this is overlap with service meshes, but that is okay Each one performs very different job depending on that north south and east-west traffic patterns A little bit more info about those specific features of emissary on the resilience side We've got things like timeouts circuit braking and retries and there are also extension points for Authentication with the X-Toth protocol and then rate limiting with the RLS Proto On observability like I mentioned we've got support for Distributed tracing and we've got tons of great metrics that are provided by Envoi so you can do things like setting up Grafana dashboard and Monitoring those metrics to see what's going on with your services Like I said emissary ingress is powered by Envoi That is the core of what it does and how it gets traffic to your back-end services You may have heard about this thing called Edge Stack That's not the focus of this talk But just so you're aware of what the relationship is Edge Stack is basically emissary ingress But with some additional features built on top of it anything you hear Edge Stack might be capable of Emissary is more than capable of on its own You just might have to do a little bit of lay work to build those things out yourself So going into the recap over the last two years what has been gone on with the project in 2021 we were previously called Ambassador API Gateway then we donated the source code to the CNCF and renamed it to emissary ingress We also had the major version 2.0 in 2021 and major version 3.0 in 2022 We've introduced new CRD versions if you've been a long-time user of the product You will probably be familiar with we've got a bunch of different ones latest one is v3 alpha 1 We've made improvements to our integrations with service meshes like linker D. Istio and console and Most recently with that 3.0 major version upgrade We've got support for HTTP 3.0 to downstream clients right now in the future We'll probably support it for upstream clients, but right now it is just downstream connections We've had a ton of releases a ton of commits and we really appreciate everyone who's gotten involved Tried out the product given us feedback and contributed to it The 3.0 why the major points were bringing Envoy up to date So we were running a much outdated version of Envoy 1.17 We brought that all the way up to 1.23 and mostly that is bug fixes security and stability improvements We also had to drop support for your Envoy's v2 API. They made that choice We were kind of forced on that but that should mostly be transparent to the users Beyond that we upgraded a bunch of our dependencies We're also now on the latest version of go upgraded our Python and a bunch of other parts of the container Like I said, we've got that new support in the 3.0 X series for HTTP 3.0 to downstream clients and One major contributor I wanted to call out was Paula Celebria who added support for custom tags and tracing services I'm going to give it over to Flynn and he's going to talk a bit about configuring emissary ingress Thank you. So Alice mentioned early on here about developer centric self-service configuration. That's been a focus That's been a focus of emissary ingress since it's start back in 2017 Let's see There we go Sorry Alright This is an example of how you would some of the things that you can do when configuring Configuring emissary. This is actually a complete emissary configuration To have emissary listening for a TLS traffic on 48443 Doing TLS with that assuming that you are using the hostname food at example comm and then routing traffic with the slash quote Slash path prefix over into a quote service If you were to look under the hood you would find that this generated an envoy config That is at least hundreds if not a thousand lines long You probably do not want to be actually messing with the envoy config in this one. The emissary configuration here is much more palatable You can do this with the ingress resource and that ingress resource is Roughly equivalent There's a couple of things that are minor minorly different here But those two the three CRD's on the left and the ingress resource on the right are roughly equivalent It's a little bit challenging though in operations to be doing this all with the same CRD You end up where if you have multiple people so for example if you decide that you want to change something about the TLS certificate While somebody is trying to change the path of the mapping You're both going to be trying to edit the same resource at the same time and things can get complex so That makes it a little bit tricky to do the whole self-service thing and now this has decided that it's just not going to work All right, I'll use the keyboard One of the things that's nice about this particular configuration language is if you separate out the mappings And then the other stuff more on the infrastructure side the way we've done You also get to separate those roles as people are working at this in operations So you can do all of this with just one person Where you've got a single person going through and dealing with all the mappings dealing with the listeners dealing with the host the authentication service the rate limit service everything else But it's very very easy to separate this into two roles or more So that you can have the developers of your application worrying about mappings and then have separate people filling the more Op-centric role trying to go through and worrying about the more infrastructure research of things This is something that's being baked into emissary literally since the start in 2017 It has been very important for a bunch of the adoption that we've got this is end up ended up resonating a lot with a bunch of users Enough so that it's kind of fallen into being a best practice at least in our heads If you look at Computing as a whole computer engineering as a whole We know very well how to deal with four or five developers on a team We kind of know okay how to deal with two or three dozen on a team By the time you're into the hundreds on it the hundreds of people who are all trying to work on the same sort of thing Pretty much the only way we know how to do this Well as with microservices where you arrange things so that you have different teams working on different chunks of the Thing all going independently all having an independent release train This is really interesting because it requires that you separate those concerns out very nicely And it also requires that if you really want the most most benefit from it You have to have all those teams able to work at full speed without getting bottlenecked either on each other or Getting bottlenecked on operations This ends up requiring a lot of trust Where you kind of have to trust your developers will have to trust that Operations is going to do the right thing and provide them all of the platform stuff that they need to get their things done Operations will in turn need to trust to that the developers are going to be Operating in good faiths trying to work on their things and trusting the ops guys to do the platforms things Everybody ends up benefiting from trust going both directions, which is Interesting because there are a lot of ways also where historically These two roles in a lot of ways and at a lot of times don't find that trust to be natural You don't have to do that trust blindly of course Kubernetes are back is a great tool for going through and putting guardrails around things so that the developers can only mess with the developer sorts of things the operators can only deal with the operator sorts of things I'm going to call out the kubectl sudo command as well We've been using that one or I guess y'all have been using that at ambassador labs for a while To great effect It's a way you can basically set things up so that normally you're just doing your normal stuff with your normal control account But if you need to you can switch over and impersonate a higher privilege account long enough to get something done There's a full audit trail so that everybody can go back and make sure that the right things have happened Kubernetes in general makes the whole audit trail thing really easy. You can always go through and pull the configuration out logical extension of that idea is the whole get-ups infrastructure is code thing Likewise Argo CD all that sorts of stuff, but all of these really get back to Constructing away where your different teams get to trust each other to support each other Where you can have guardrails, but you can still have everybody working at full speed without having to be blocked on each other It is a lot of effort, but that's okay. It's worth it All right, any questions about any of that so far before we talk a little bit about the version 3 crd's and where those are going All right, just as in general we're gonna be hanging out afterwards You can always come up and talk to us afterwards. I expect that we will end up with time for questions at this point so Let's talk a little bit about the b3 crd's And we probably get to slow down quite a bit at this point too, so Okay If you take a look at these crd's you will notice that they all say get ambassador dot IO slash v3 alpha 1 There's been a lot of discussion about the transition from Get ambassador dot IO slash v1 to get ambassador dot IO slash v2 to get ambassador dot IO slash v3 alpha 1 To oh great v3 final is coming. What should we do with that? We already are pretty sure about a couple of things that we want to do with this transition One of them is a lot of cleanup stuff if you look over at that yaml over on the right You'll see a bunch of things where we have fields that are named with underscores in snake case So we know we want to shift those things over to camel case because it would be kind of nice to do that the way The entire rest of the ecosystem does Sorry about that We know for example that we would like to be using durations instead of having things named with underscore ms or underscore s or whatever right We know That there are some fields that are deprecated but still present now a good one is there's a use web sockets fields that We really should just throw away entirely. You can already use allow upgrades web socket And we recommend that but at some point the use web sockets field is going to go away likewise Host and host regex get combined into a single host name regex thing And so there are quite a few things like this that live in the CRDs as they stand right now And I Am going to let Alice go ahead and talk about other stuff on the way to be three over to you Thank you So, yeah, a couple other consistency improvements We want to make to the CRDs when we're going to be three final is that we've got a bunch of different services Like the auth service the log service mappings These are all things that result in Envoy cluster creation But what's inconsistent about them is that you don't necessarily have the same convict options through our CRDs So one thing we'd like to standardize is across any resource that lets you configure For example Envoy cluster is just one example You should be able to configure the exact same things like timeout snap settings, etc Across all of these different CRDs So there's not this disconnect where a mapping allows you to configure one field but another CRD that creates a similar Envoy resource does not allow you to configure the same field or in instances where Maybe the field is being configured in both resources, but the naming and how you configure them in our CRDs Is inconsistent so that's something we'd like to fix What is the path going to look like for v3? Well, we're probably going to be doing a v3 beta one sometime soon We're not really firmly committed to any sort of a timeline on this We are mostly just watching around what the community is letting us know about the v3 alpha one CRDs Changes that they would like to make we introduced some of those things that we'd want to mention Sorry that Flynn mentioned in the previous slide We want to change such as the inconsistencies in the snake casing that we want to do That was brought up in Las Valencia cube con So we haven't heard a lot of feedback about that when we were in the other We're going to take that as that this is something the community is okay with but um We're always having conversations with people trying to figure out What are the things that people like and don't like about our CRDs? What changes do people want to see what things do they want us to not change? We may or may not end up doing a v3 beta 2 That's just going to depend on priority and what all goes into v3 beta one and what we want the v3 final CRD to look like Main thing to draw attention to is that we are currently still supporting the v2 CRDs We actually dropped support for the v1 CRDs earlier this year But we are going to probably end up bringing support for v1 CRDs back Just because we've heard there have been some friction points with us dropping support for them So main thing going forward is just that all the resources you've created all the CRDs You might already have if you're a current user of emissary those aren't going to become invalid You're not going to have to go and recreate all these things We're going to support these versions moving forward, but we're going to try to make new versions of the CRDs cleaner So the storage version is not going to change to v3 final until we release v3 final So if you're just coming out with like v3 beta 1 v3 beta 2 those are never going to be storage versions Main thing to focus on here is just that if you are a user of emissary or if you're interested in it We'd love everyone's feedback on any changes They want to see or do not want to see in the CRDs if you feel strongly about that Then please create a GitHub issue reach out to us on Slack. We'd love to hear from you Another thing I want to touch on really quickly is that a lot of people who have been using the product for a long time May have been aware of the friction from the 1.x to 2.x major version migration Particularly around the CRDs. Thankfully we have learned a lot in that time So we were trying to make sure that every other major version bump going forward Is not as is not as much pain as that 1.x to 2.x jump was Also, there's this thing called Envoy Gateway Um, this was announced in kubecon valencia this year So there has been a ton going on with this project some quick recap about Envoy gateway What does this mean for emissary ingress? So as I mentioned we are built on top of Envoy proxy Eventually once we feel like Envoy gateway is in a good spot where it's pretty feature complete and stable We will start to transition to emissary ingress being built on top of Envoy gateway instead of on top of Envoy proxy directly So what is the kind of driving factor for doing this? We've got two major cncf projects that are api gateways There is emissary ingress and there is contour There's also a bunch of other people that have interest in the api gateway space And opinions about how things should go or people who are working on similar projects We want to bring as many people as possible who are working on these different things that are duplicating a lot of that api gateway effort That is just like watching resources Updating the Envoy config translating from like crds to xds config That's a lot of that's a lot of effort that's being duplicated across these various different projects So the goal of Envoy gateway is to bring in a lot of these people who have developed expertise over The lifecycle of these projects and get everyone to focus on building one common core that we can all share And that's going to be Envoy gateway So it's better to work to work together to build something solid from the ground up Rather than duplicating that effort and having a bunch of different competing apis and standards This also doesn't mean emissary ingress is going away There's a bunch of things that Envoy gateway is not going to do if the emissary ingress is going to continue to do We have already been working on both in parallel. I am a maintainer of emissary and Envoy gateway So we're going to make sure that the project is Shaping up to where we can definitely use it and make it an improvement for all the users of emissary You're not going to see emissary be replaced by Envoy gateway and we're not going to stop working on emissary So like I said long term, we're just going to eventually Support Envoy gateway as the core of emissary ingress initially We're just going to start by using bits and pieces of it as an api So that way when we feel like Envoy gateway is doing something particularly well We can integrate a little bit of it. So it's one piece at a time instead of one big jump from Envoy proxy to Envoy gateway We've been working with them to ensure that everything that we need To accomplish as emissary ingress is possible with Envoy gateway and that Envoy gateway doesn't become a limiting factor So like I said, there are certain things that Envoy gateway won't do that's where emissary ingress is going to come in Envoy gateway is only going to support the gateway api CRDs and only Kubernetes resources So emissary ingress supports for example the console service resolution That's something Envoy gateway has no interest in doing and emissary will continue to do Emissary will continue to support its existing CRDs So all that stuff that we just talked about isn't going to become invalid once we accept Envoy gateway as our core you're not going to be forced to switch to gateway api CRDs if you don't want to And I'm going to hand it off to Flynn for some recap Thank you all right so Emissary is always focused on developer centric self-service ingress configuration Simply because it's a great way to let everybody get things done more quickly This takes a lot of trust It is worth it. It does work really well And you know the trust is a good thing in the first place, right? Um, if you are a new adopter or if you're going through and adding things to your emissary ingress configurations Use v3 awful one It will be happier and nicer And it'll be a smoother transition to v3 final when it comes out Even though v2 is still supported and as Alice mentioned we're actually bringing back support for v1 Just to remove some migration friction that people are experiencing um I think that's the next dot y that that'll be in right? um We are involved in the envoy gateway Alice is a maintainer luke's also a maintainer I show up and heckle a lot, but i'm not a maintainer Uh, we're involved in envoy gateway because we believe it's a win for everybody Arranging it so that we and the console folks are not constantly duplicating the same stuff over and over and over and over again freeze everybody up to Really do more things that are new and different and interesting. This is a good thing Emissary ingress will still stick around because there are ways that emissary ingress gets to add value on top of that Likewise, I expect console will still stick around because there's contour. Did I just say console a minute ago? contour ever so sorry to all the fine people who work on console and counter um Yeah, I expect that contour will also still stick around because it too will be adding value for its customers in ways That the envoy gateway is not going to want to do community stuff I said this in valentia. I said this before in marcelona. It's there's no possible way that emissary ingress would have made it this far without the community Many many thanks much appreciated You can find the two of us if you want to get involved with developments Or if you want to ask questions or if you want to provide feedback or if you just want to say hi You'll be able to find both of us on the community slack at a8r.io slash slack That is very hard to say she's at a loss go i'm at flinn and um Yeah, thanks note alice at data wire dot.io, but flinn at buoyant.io and I think we have What five ten minutes for questions so any questions And we're also going to be sticking around afterwards So if you just want to come up and talk and instead of shouting your question out, that's fine, too Hi, thanks for the talk if somebody's running istio for east-west traffic Is there a way for ambassador to route directly to pods or would it need to be like a Have its own istio sidecar There are a lot of answers to that question um as of I mean, I know i'm going to get the istio versions wrong, but for a little while now it has been possible to have emissary Watch the mtls configuration for istio And then just simply participate in the istio mesh Without having to be fully meshed in with its own sidecar from istio, etc, etc I'm pretty sure that you can do it by injecting emissary fully into the istio mesh But if you do you have to make sure that you change the envoy of base id for one of them either istio or emissary So in most situations, it's going to be simpler just to let emissary watch the tls configuration and do it that way Does that answer the question? probably Try it. Let us know what it's at. What happens anything else? I've got a question. Um get ambassador In the url there for the Any any chances that's going to change? Oh, that is a lovely lovely question um Well, actually, that's a good question. Are you talking about in the crd definition? Are you talking about the url? Yeah, yeah in the yeah, okay, so There was a fair amount of discussion about that and the conclusion was that it was Probably more of a headache than it was worth for existing users to change all of their api groups um, I see some nods in the audience It would be technically possible to support both sort of but We've never heard from anybody that that was a real thing that the community wanted So if you are in the community and you do want this, let us know um, otherwise nobody Everybody seems to be looking at it as oh my god, this would be awful for migration Any other questions anything else? I don't want to hug mic, but I've got another one is the um Is the envoy gateway a wrapper around the envoy proxy or a rewrite So it's meant to be a wrapper around the envoy proxy. Um Actually, we just had our first um functional release of envoy gateway just a couple days before kubecon If you weren't able to attend the envoy gateway talk, um mean features of that is that um envoy gateway will spin up a bunch of um Envoy proxies um as a fleet it uses the gateway api so while emissary has um it configures envoy by um being In the same container where we've got like one pod it contains both the processes for emissary ingress and envoy um envoy gateway actually has separate deployments You've got like your main envoy gateway deployment that will listen for like gateway resources Which will instruct it to create envoy proxy deployments that it will manage Got it. Thank you Any other questions? All right. Well, thank you guys very much Yep, thanks for everyone coming