 Welcome to KubeCon EMEA 2021 and my lightning talk. I'm Rob Esker from NetApp. I'd like to offer to the extent that I can within five minutes a few of our observations from NetApp in our years of having worked with the employers and of course as practitioners ourselves. A few things, primarily from the lens of storage and data management that hopefully can inform how you look at and approach and operate Kubernetes. Let me just start with a little bit about NetApp. I mentioned or alluded to, we worked with many thousands of customers since the inception. We contribute to the storage sites, data protection working group and of course the container storage interface specification as well. Our customers brought us to the conversation. We use Kubernetes ourselves to power many of our cloud services. We'll have more to talk about on that in actually the coming months. So this is not just a scenario where providing capabilities vis-a-vis Kubernetes but also building our own products based in part on Kubernetes. So a little bit about, I guess on the editorial end about Kubernetes. I'd offer that we have seen from our customers kind of a realization or a epiphany process of epiphany where there's an understanding that Kubernetes is maybe not necessarily strictly just an evolution of more hypervisor VM based classic infrastructure as a service that indeed it's a predominantly a desired state machine, particularly useful for automating scaling and life cycle of applications. Mostly thought to be predicated on containers but actually not entirely confined to that when you look at things like Q-Verb. That said, it's an important sort of calibration at the outset that there are some things that are a little bit different about Kubernetes than what you might have expected from a VM and it surrounding ecosystem as a runtime. So just to start with that, one of the things in particular, if you add kind of a time dimension to understand Kubernetes is at the beginning it was really built of, can I take a quote unquote cloud native application built of a 12 factor application model, which maybe didn't necessarily really kind of thought that the only way to persist data was in an object. And can I deliver it and of course it did that well but that was a bit limiting in terms of the style and kind of computational problem for which Kubernetes could be applied. So it was certainly the case that from the outset we seek to engage to help in the community context evolve a more sophisticated construct a lot CSI for accessing distinguishing qualities of storage not strictly it's an object here but like I have something that I have multiple access modes to interact with perhaps many writers against a common bite range. There's different access modes that have evolved in Kubernetes for accessing data sets. There's a notion of storage classes for which you can define distinguishing capabilities that one application may demand versus another. And from a net perspective we have provided those capabilities in all of the public cloud most recognizable public clouds in a variety of different services. We've wedded them to Kubernetes with a project called Trident and we built that into a new capability called Astra which takes sort of an application centric perspective of delivering sophisticated persistence that's portable in the same way that a work an actual application itself may be portable for Kubernetes from one place to another whether it's across the public clouds or on-prem. You know a few things I'd also offer just kind of rapid fire style in terms of things we've seen do not perceive that default security you know intelligent defaults aren't necessarily always accounted for vertically across the entirety of the stack. You know secrets are they in fact secret actually no they're not the case I encourage you to look at Kubernetes documentation actually by default everything's stored as an unencrypted string they can be retrieved as plain text by anyone with you know the necessary API access. Think about the underpinning persistent volumes and who has access to it and from what layer. So security is not necessarily a simple topic I have heard in the most recent cloud native computing foundation governing board meeting only 6% of the folks who have attempted the CKS examination so far have passed it. Now that's early data that could change the point is it's not a simple topic. I do want to make a quick plug there's a ton of topics we'd love to engage with you on at NetApps Virtual Booth here at KubeCon and thank you for the opportunity and your time. Have a great KubeCon.