Thomas Giacomo10:29
Let me start with the aspect of combining things together. Daniel, maybe you can take the management piece. We are making sure at SUSE that we don't solve just for one type of pool. We have the SUSE stack and we are very happy people use it. But the reality is that our customers, they have some investments, they have different needs, they use different technologies from the past, probably want to try different technologies. So you have to make sure that for Kubernetes, like for any other part of the IT stack or the developer stack, your pieces are modular, that you can accommodate different elements. Typically at SUSE, we support different types of hypervisors, we're not focused on one. We can support KVM, Xen, Hyper-V, vSphere, all of the net new TENEX hypervisor, and everything. Same thing with the OS, there's not only one Linux that people are running, and that's exactly the same with Kubernetes. There's no one that I've seen in our customer base that will just need one vendor for Kubernetes, because they have hybrid cloud needs and strategy, and they will benefit from the native Kubernetes they find on AKS, EKS, GKE, Alibaba Clouds, you name them. And we have partnerships with those providers as well doing that. So for us, it's very important that what we bring as SUSE to our customers can be combined with what they have, what they want, even if it's from the so-called competition. Cloud Foundry is running on AWS, you can find it on the marketplace of public clouds, it could run on any Kubernetes, it doesn't have to be SUSE's Kubernetes. But then you end up with a lot of clusters, right? So how do we deal with that, Daniel?