 I will be talking about GitOps sustainability with Flux and ARM64. My name is Tomo Nakahara, and I work at WeaveWorks. I presented a longer version of this talk yesterday at GitOpsCon with Liz Fong-Jones over at Honeycomb. So if you're interested in the longer version, please reach out to us or see the recording. So I think we're in a recession. A lot of people talk about it, or if we're not, we're still looking for ways to make sure that we're being smart with our costs and especially supporting sustainability at the same time. And as technologists, of course, we look to technology to see if we can find solutions. So this talk will cover an actual test and great results in which we turn to technology to do that. So ARM specifically is a commercially available on many cloud providers and increasingly is becoming an alternative to x86. So we like to look at the cost savings as well as the environmental benefits. And I work for the company WeaveWorks that coined the term GitOps, primarily from this project Flux, which is in the cloud-native computing foundation. And GitOps is this idea of operations by pull request in which you have a repo with a manifest, often a YAML file, which states the single source of truth of the cluster. And what Flux does is it listens to that repo. And if it notices a change in the YAML, for example, it'll tell Kubernetes, hey, make sure that the cluster is meeting this desired state. So you can tell me this is a pull model. So we're doing all the things that we can to make sure that we're not using excessive resources unnecessarily. And this one solution at looking at ARM64 is really exciting. And not only that, Flux will make it easier for you to migrate to that if you're interested. Especially Flux ships with multi-arch images like ARM64, ARMv7, and Intel AMD64, which makes this demo that we had yesterday possible. And you can also do it with progressive delivery without making changes to the config. So Graviton 2 was announced in December 2019, and that version made it so that it was quite compellingly competitive with X84. So Liz over at Honeycomb wanted to test this out and actually has a great blog post on it. If you haven't seen it, go check it out. So a few considerations. So if you're using Python or Java, you're good because they are kind of architecture independent. If you're using C++ with hand-assembled stuff, there's some updates, and Honeycomb is a go shop. So there's a few things that they did. So first, they set up ARM64 cross-compilation instance, and they made sure that their CircleCI config included a build step for an ARM64 target. So once they had those configurations in place, or the considerations in place, sorry, what they first did is they started with one Graviton instance in an auto-scaling group, and then they set up Terraform to build instances at each different stage. And then when they got it to 20%, they waited a couple of weeks to see how it went. And the results were astounding. They had a 35% reduction in cost, which they wrote about, and we are both really excited that you can go on that journey as well. The thing is that, as you can see here, from July to October, it took them many months to get this done. And as we were chatting, they were saying, well, yeah, because we weren't using Kubernetes. There was a lot of manual steps. But if you were to use GitOps with Flux, you could do what they did in a day if you have a similar setup. So that's what we're really excited about is not only these benefits, but also the fact that with GitOps and Flux, you can do that. So how would that work? As I mentioned, Flux listens to the repo and notices a change in the YAML file and makes sure that Kubernetes does the reconciliation. So in this case, in the demo that we showed, for the instance value, we had AMD64. We just typed it in and changed to ARM64 and saved. It's operations by pull requests. So if you want a full pull request version, you can also do that with approvals and audit logs and all that. But when you do the Git push, in this case, we showed how then you could update your architecture to be pinned to ARM64 simply by changing the YAML and GitOps does the rest. And moreover, like I said, Flux allows for progressive delivery. So if you wanted to have canary deployments, you can do that as well. So we're really excited that not only did Flux make this easier, but it gives these gains and benefits. And in fact, if you want to go back and forth between ARM64 and AMD64, you can do that as well. Please check this QR code. We have plenty of talks here at Open Source Summit and we just finished GitOpsCon and CDCon on all these types of talks that cover Flux. Our company is Weave.Works. So our contact info is there and if you want to find out more info, please reach out to us. Thank you.