 A lot of the things that we've been seeing today, these complicated databases, these complicated applications, the beauty of the operator is that the complexity is programmed into the operator and frees up the administrator to do what they do, rather than worrying about the specific application. But of course, the problem with that is that you then have to write an operator and you have to lifecycle that operator. And so the operator framework is a project that's attempting to solve those problems as much as we can to make writing operators easier for all of you. And it is, of course, open source. And as of 2020, we are a CNCF incubating project. We have over 200 individual contributors at the moment. And I put the link to our community revoke here. We've been divided into working groups as well. So we've got operator SDK. That's what will scaffold, help you test. Operator lifecycle manager will help you manage your lifecycle. And then we've got some language-based individual meetings. So operator framework can help you write operators in Helm, Ansible, Java, Go, and more coming. And I will also give you all of these links that you'll never remember. But the big one is the website, our GitHub, and this mailing list. If you subscribe to that mailing list, you'll also get our calendar invites as well. We're also around on Slack. And we are very friendly. We accept newbie questions. We accept advanced questions. We just like to get feedback. Because in truth, operators are such a wide field that there's just so many use cases that we could never dream of. So we need to hear from everyone, what are your use cases? What do you need from the operator SDK? What do you need from all of them? How can we help you do that? But that's about it for me. But do feel free to ask me any questions now, or join us in Slack or whatever. And we'll be very friendly, I promise.