 So with that, I can move on to the next main topic of the day, which is our fully self-hosted Pixie install. And we don't know what we'll be doing the demo on this, but this is one of the issues. Issue number 238 actually in our repo, which has gotten a fair amount of attention. So something that we've prioritized pretty highly on our list. And currently with Pixie, there's basically two different ways of working with Pixie. The first one is a community cloud for Pixie, which is basically a free forever cloud hosted by New Relic. And you can basically utilize that. I got all the features inside of Pixie. It's basically our open source version of Pixie that's hosted. However, if you want to use Pixie completely by yourself, you can host a version of Pixie Cloud on your own infrastructure. Honestly, this is still a little bit of a work in progress. So we're still trying to test out different configurations. But please feel free to give it a try by following the instructions here. And let us know if you have any feedback. And there are a couple of known issues that have been documented in the issue tracker. But other than that, it should be good to use starting now. With that, I'll let Weehan take it over and do a demo. OK, let me just share my screen. OK, so I have done a few live demos in the past. But instead of having to make everyone wait through watching a Kubernetes deploy, I took some time this morning to just record this demo out. But I'll walk us through it and show you how you can deploy Pixie Cloud today. So while the entire source code of Pixie is open source, we also took the additional step of making pre-built images for all of our Cloud jobs available. So you don't actually really have to build anything right now. So this assumes that you have Pixie's open source repo checked out. And we tested the demo on GKE, which is our current deployment environment for Pixie Cloud. And we'd love to see community feedback on whether it works elsewhere. And we're happy to help make it work elsewhere too. So for the demo, we just want to create a namespace for Pixie Cloud to run in. We have a little script that creates a few secrets and deploys them to that namespace. So these secrets are sort of things like session cookies or JWT signing keys and some TLS certs, after which we need to deploy the dependencies for Pixie Cloud to run. So this set of YAMLs will bring up elastic, NATs and stand and Postgres. We use elastic too for indexing NATs and stand for messaging and Postgres is the DB for Pixie Cloud. You have to wait a little bit for all of these deployments to stabilize. And hopefully that happens quickly. And then once these deployments are stabilized and ready to go, we can continue forward with deploying the rest of Pixie Cloud. So now that our deployments are good for our dependencies, we can go ahead and deploy the rest of Pixie Cloud. And that's another set of YAMLs built by Customize. And this brings up the rest of the Pixie services. Now, this Pixie Cloud is running on GKE. So we need sort of a DNS setup. We have a little tool that we use internally called DevDNS Updater. So you can just build that Go tool and then it will update the Etsy hosts on your machine to point to the IP address for the Pixie Cloud running on your Kubernetes environment. So you can just build that tool quickly and use it with the given flags. And that will update the DNS entries on your host machine. And then as part of Pixie Cloud, we wanted to reduce dependencies on some of the vendor stuff we use like OAuth. So instead, we are using Hydra and Kratos from Ori to do all of our user management and do username and password-based login. So as part of that process, we create a singular admin user when you first deploy Pixie. To set up the password for the admin user, you want to find the create admin job. And we'll get logs for the admin job. And the logs will give you a recovery link to reset the password for this admin account. So we'll just go to that, set a nice password for admin account. And that is Pixie Cloud running. At this point, we can use the Pixie CLI. So since this is your own Pixie Cloud, the Pixie CLI will now want to talk to that cloud and not want to talk to our publicly hosted, our Pixie hosted cloud. So you need to export this environment variable. And then the CLI can log in. And then we use the admin user and the password to be set. Note that once you have this admin user set up, you can go ahead and create. This admin user can go ahead and create accounts for other people on the same instance of Pixie Cloud and send them recovery links to finish setting up their own accounts too. But for now, we'll just continue using this admin user. And then we'll go ahead and deploy Pixie itself into the same cluster pointing to this Pixie Cloud. So this is deploying Pixie's Vizier objects to the same Pixie Cloud. And once the Pixie deployment stabilizes, we can quickly use the CLI and test out running Pixel scripts. And then as you can see, we can now get output from Pixie running on this local development version of Pixie Cloud and talking to the Pixie deployed in that cloud. Yep. As Zayn mentioned earlier, there's a couple of... This is still a work in progress and we're trying to smoothen out the edges as much as possible. There's a small bug with the UI right now which we're in the process of fixing. So you will be able to also access the UI just like you did with the live CLI here.