 Hello, everyone. My name is Yosemite Cordova, and I am a software engineer at Red Hat. And I work in the Kiali project. And in this lightning talk, I'm going to show you how to visualize these Istio ambient components through Kiali. So Kiali is an observability console for Istio. And it has an overview page with information in the cars about our control planes and also about the namespaces. And when Kiali detects that there is a Cetanil diamond set, it will show this ambient label in the control plane car. It's important to know that, for example, Kiali doesn't detect that there is any Cetanil diamond set. It is not going to add any other features that I'm going to show later, because this is still an alpha feature, so we make sure we are not going to add any of this logic into production. And the same way, this is adding this label into our control plane car, Kiali also adds this ambient label when it detects that there is any label data plane mode equals ambient in our namespace. So we know this is an ambient namespace. This is a workload details view. And when Kiali detects that our pod is captured or the traffic is redirected through Cetanil, it's going to show the Cetanil label next to our workload's name. And before ambient, when we are not in an ambient mesh, we know that our workload is added into our mesh because of the sidecars. But now with ambient, we are going to have different components. And this is the way to show us how. When also our workload has any waypoint proxy, it's going to be labeled like this. And we can also see our waypoint proxies in our mini graph. So this is a graph page. And here, our waypoint proxies are going to be hidden by default because they are considered as part of the infrastructure. But there is going to be a new display option that is called waypoint proxies in case we want to show them. This is an example of one of the features that is not going to be here if Kiali doesn't detect that this is an ambient mesh. So this is our workload's list page. And before ambient, when we didn't have our workload included into our mesh, we can see a message, a warning message, that indicates that our workload has a missing cycle. But this message doesn't make any sense now with ambient. So when Kiali detects that our workload is not part of the mesh because it doesn't have any cycle or because it doesn't have any traffic redirection through C-Tanel, now it's going to show this out of message. This is a graph page again. And this is to show you how the telemetry is going to change the way we see the graph in ambient. So before when we are not in ambient mesh, we are going to see the edges that we're showing the actual protocol of the request. For example, when we have a green edge, we know this is going to be an HTTP request. Or when we see a blue edge, this is going to be because it's a TCP request. But with ambient, this is going to change because it's going to represent the component in which this telemetry was reported. So, for example, we have here some blue edges and they indicate they were reported from a C-Tanel and even if maybe they are an HTTP request and we have our green edges that represent the telemetry that was generated from a waypoint proxy. So it looks like we have like duplicate edges but this is the reason why. It looks different with ambient. And yet this was a summary of all the changes that we have done in Kiali to support Istio ambient but this is still an alpha feature that is continuing evolving with ambient. How the telemetry is looking for ambient is something that is still under definition that probably will change the way that Kiali creates the graph from that telemetry and probably will help to simplify it. And as future ideas for work, we are going to work on how to visualize these logs that are now associated to our workload, how to create waypoint proxies through withers in the same way that, for example, Kiali allows you to create Istio configurations through withers in a graphical way or how to include some C-Tanel indicators in the graph. So thank you everyone and don't hesitate to reach out to me or the team through our Github project or Slack channel. We have any questions, go for it. This is limited to the network protocols you showed here. There's no, for general network protocols like UDP, SCDP, there's no solution, I think. Sorry, can you repeat the question? The question is about the network protocols, Jeff. HTTP, TCP, GRPC. And what about other network protocols like UDP, SCTP, and so on? Well, at the moment, Kiali just represent these kind of protocols and this is based on what is the telemetry that is reported by Istio. So if we don't have this data reported, we just got these protocols that are reported through using different metrics and that's the reason why we just showed these three protocols here. Hi, any news on visualizing multiple clusters? I know that there has been one new feature about it we have several Istio D replicas running multiple clusters so we don't know how to bound that without having a single gigantic Prometheus and so on. So any news on that? Well, recently we have finished all our features that we have for Alpha support for multi cluster. Here you can visualize different workloads in different meshes for primary and primary remote support that it has like still some things to be working like for example, the authentication methods that is still just an anonymous and open ID is available right now. But if you want, there is a list of all the features that are already supported in the Kiali release page. Awesome, all right, thank you. Thank you.