 We're going to start, all right, I think we're going to get ready to start because this is a live stream. So there's no point to wait. I know this is the end of the day. So thank you so much for being here. Really appreciate it. Today, we're going to talk about Operate Psycho and Psycho List application with Istio and Argo Rollout. My name is Lin Song. I'm the director of open source as solo.io. How many of you heard of a small company? Oh, yeah, a lot of you. Thank you. Awesome. So how many of you know Istio? Service mesh architecture. Okay, I don't need to explain the slides because you guys know we have Psycho architecture. The control plan is programming the Psycho to do intelligent things such as policies. How many of you are aware of what driving a new architecture called ambient in the Istio community? Wow, many of you. Okay, good job. So essentially, what we are involving ambient is what if you don't need to drag that cycle along with your application? What if you just need layer for functionality? We would provide a per node proxy for you that implement the layer for functionality for you such as layer for authorization policy, layer for traffic management. So that's what we are involving in the Istio community. What we are also involving is also split the layer for and layer seven into different architecture where layer four is implemented per node proxy, which is the orange thing you see here that's called zero trust tunnel. And then the layer seven is implemented by waypoint proxy continue use our favorite proxy, which is our way proxy. So today I'm going to talk you through my journey of using our go rollout with applications running Istio ambient. So how many of you have used our go rollout with Istio application with cycle a few of you. Okay, I actually saw a bunch of a tutorial on that. So I'm not going to focus primarily my talk on that just because it's already been known how to do that. There's very clear steps on how to do that. One of the things is you can potentially run your application with cycle and the application without cycle in Istio. They can talk to each other, right. So and you can continue use our go rollout to roll out your updates seamlessly whether you're using cycle or without cycle. So because I'm doing a lightning talk. I have a lot of screenshots for you, but I could do a live demo if I actually have more time since I only have five minutes I'm just go through the demo in a screenshots format. So the first thing I'm going to do is I'm going to deploy our go application in our go rollout. And this is a really simple application where I deploy a hollow word. I have a successful criteria for rollout through a rollout analysis template. I also have Istio virtual service and gateway resource. These are used to config traffic come into the Istio Ingress gateway to hollow word. So as you can see, everything was synced okay in this example, and I'm using this GitHub repository, which is open source by the way and then I specified the past when I create the Argo application. So what I'm doing next is I'm rolling out a newer version of my hollow application using Argo rollout set image command. And then I'm checking out the rollout status throughout the process. So the first time I come in, you know, I would see the step is on zero. And we're just started to, you know, look at the canary, get it deployed, the containers are creating. By the way, if you look at here right now, you can see my hollow word. Without any of the cycles, right, that's what a one slash one zero slash one means. So my hollow word version two is trying to come up with the new image. Now, as I'm checking out my rollout status, you can see right now it's three slash eight, which means we're halfway almost halfway down. I pause because in the rollout analysis template I try to in the rollout configuration I try to roll out pause every 20 seconds just making sure the results is consistent. And you can see the analysis is running, you know, I got one checks. So that's why it's moved forward from zero slash eight to three slash eight. So let's continue forward. It's continued a rollout to five slash eight. In this case, it means a little bit more than for 50% of the traffic would go to hollow version two. And then the remainder lesson lesson, which by the way, you can see the weight here I forgot. So 60% is going to version two 40% is going to version one. And the the rollout is going really well. And in the meanwhile, you can also see the virtual service by the way the virtual service resourcing is your means the traffic route configuration. And you can see the current virtual service resource for the Hollywood on my system, which is how the program away is down by version two have 60% and version one which is the stable has 40%. I also have another terminal that shows the current result goes to hello word service. And you can see it's roughly about 60%. It goes to version two. Let's continue checking out the rollout status right now it's eight slash eight. And now it's 100% goes to version two, which you can see the version one of hello word it's getting scaled down while the parts being terminated. So that's pretty much the final stage of the rollout and then you can see 100% goes to version two. One thing I want to highlight this is new with ambient is I actually deploy a waypoint proxy right we talk about waypoint proxy architecture a little bit early in ambient right so waypoint proxy is the key that helps does layer seven traffic management layer seven traffic enforcement. Before I started my rollout I deploy the waypoint proxy to help facilitate that traffic shifting. At the end, after I roll out to version two I no longer need to have the waypoint proxy so I no longer needs to pay for the cost to run it to operate I can actually remove it. I actually removed the waypoint proxy to save the cost. This is very different than cycle because with cycle you can't write a cycle is going to be with you regardless of whether you're on version two or after your successful rollout. In summary, Agile rollout continue to work with application with cycle or without cycle moving application from base version to canary version are very helpful using Agile rollout. In my opinion Agile rollout is actually made a lot easy and also flexible by you only pay for waypoint when you really need it with your ambient. So check out the GitHub repo and play with this yourself. Thank you all for attending my talk. I will be I don't think right any talk has time for questions so I will be around if you guys have any questions. Thank you.