 Up next, I would like to invite my dear friend, Hin Goldberg, to join us from Google. Hin is the head of engineering for Google Kubernetes Engine amongst many other things. And I'm going to come out and talk about Kubernetes and another project she's really interested in. Come on out, Hin. Thank you. So happy to be here. Thank you for inviting me. Welcome to Boston. It takes us coming to Boston to hang out. We are so thrilled to have you join us today and obviously interoperability plays a big role in what we're talking about this year and Kubernetes. But I want to talk a little bit about the work you're doing running the engineering team for Kubernetes, but also some of the other open source work that you're doing. So for me, everything starts with the users, right? People here sitting in the audience, Google users, and really understanding their pain. And you started talking about it that today our role is much more complex. And our work, we have much more work to do. And this is where something like Cloud Foundry really helps us to deliver things quicker and improve our agility and velocity. And we all care about that. And my team, and definitely with Kubernetes and the thing we're thinking about in Google is the question, can we broaden that? Are there workloads that we cannot modernize? And I think the answer to that is no, we can modernize everything. It's about trade-offs. It's about decision. We talked about control before. So how can we balance between flexibility and consistency? And this is something I've talked about in KubeCon, how I think Kubernetes is doing a good job balancing between the two and allowing you to achieve that velocity in more workloads, like stateful workloads that are really complementary to Cloud Foundry. Absolutely. And we're obviously big fans of Kubernetes. You also run the Istio engineering team. Yes. Which is absolutely dear and dear to our hearts. It is. It's another standard that we hope that will be really adopted by more technologies in the Cloud Native Technologies. And I think that also speaks about some of the principles and values that you will find in the Kubernetes community and Cloud Foundry. And also Google, share between the projects. So the first thing is, of course, working in open source technologies. We care about portability. And again, this all ties back to the users, to everybody, to our pain. We want to run our systems everywhere. We want to make sure that we are not being locked in. And this is where, and collaboration, right? You also mentioned that that's really a lot of value of open source. The second thing is extensibility, where you can extend and build on top of the technology. And the last one I want to highlight is open standards. So Google and Cloud Foundry and Kubernetes community has been working on several open standards recently. So you mentioned OCI, CSI, Cloud Container Storage Interface that went beta in Kubernetes 1.10 just a couple of months ago. And by having those open standards and extensibility in open source, this is where we can build those composable systems and really allow us to modernize and mix and match different framework, different languages, different platforms. And before going to Istia, I want to announce that I really think that anyone on any Cloud Foundry user, if they will come to Google Cloud Platform, they will feel like home. Because all of those principles are things that we all live based on. And I'm happy to announce that next we will make our managed service broker based on the open service broker API beta. It will make it very easy to consume any GCP service starting with things like BigQuery and Google Cloud Pub's up from any Kubernetes cluster. But also it supports Cloud Foundry, so supporting this interoperability that we talked about by open standards. And when I think about that, I mean, we've thrown out a lot of things. We've talked about open service broker API and Kubernetes and Istio. But how are they all combined? And what's the point? And I think where we keep coming back to is the services and extensibility to your point. So where do you see those things coming together in your mind? This is where Istio comes to play. This is a great segue for Istio. So we talked about modernization, that it can happen on different platforms. So Istio is creating an abstraction and decouples the service management from the code itself that builds services. So think of how you can achieve consistency, for example, with control, traffic control, authentication, for example, with telemetry, observability into the services, regardless of where those services are being deployed or being built on whatever platform. And it's, of course, based on Envoy and the proxy, by, again, leveraging open source technologies. And I feel that by building that framework, we can continue and allow flexibility, but without compromising the consistency. So if, for example, you want to apply a new policy, you can do it simultaneously on all the services, regardless of what platform. It can be a Cloud Foundry service, a Kubernetes service, a Google Kubernetes Engine service, or just bare VM, which is super powerful. Because at the end of the day, it's really going to be about services and the availability of those services. Yes, I agree. Which is exciting. And actually, I want a quick question, because we've thrown around a lot of these technology terms. Does everyone here know what Istio actually is? Maybe you can give a quick overview of what Istio actually is, because I think it's a pretty new term to the Cloud Foundry community. And I know that it's still not 1.0 yet, but it would be a good primer on what Istio is. So I will also tweet afterwards a great talk, but one of the product managers, I think, makes a great job explaining Istio. But in essence, it's really decoupling the service management or operation of the services from the code itself. So we're actually putting proxies everywhere in front of the service. And what it gives us, it gives us a consistent layer to manage and manage the traffic, for example. So it gives you control, observability, and security layer on top of those services. And what we see from users, so this might seem like a very big change for you, but what we see users doing, they're choosing pieces of the Istio framework for their own use case. So if you really care about telemetry and you want to make sure that you have all the metrics coming from all your services, then you can use Istio for that. Or if you care about ensuring policies or traffic management, for example, then you can choose other things with Istio. That's awesome. Well, I, for one, am really excited about what's to come with Istio in Kubernetes in 2018 and beyond. And we're so thrilled to have you join us and talk a lot more about that with our community. Thank you so much, Hind. Thank you very much, I think. Bye.