Last week, I was at KubeCon Europe, at our Cloud Native Security Day on a panel with NIST and Red Hat and meeting with many customers and partners. By now, you’ve probably already seen our news about our intent to join Palo Alto Networks – being at KubeCon really reinforced the momentum around this technology and why being able to go both deeper and broader as part of Prisma is so exciting. Some thoughts:
Continued huge YoY attendee growth – I remember going to the first KubeCons when there were just a few hundred attendees. Barcelona hosted 8000 people for the event, almost 100% larger than last year in Copenhagen!
There wasn’t much earth shattering news or major new announcements – and that’s a good thing! For enterprises to adopt a new technology generation, they need consistency and predictability. In the early days of cloud native, having constant innovation churn was a good thing but made it difficult for users to understand what technologies were going to win out and, thus, where to invest their time and money. Today, there’s more stability in the ecosystem, revolving around Kubernetes as the center of the cloud native universe. This enables innovation to be more orderly and enterprises to feel comfortable investing in it.
A huge variety of Kubernetes options – but all fairly consistent with upstream. There are seemingly countless options for consuming the platform, from entirely provider managed cloud offerings, to companies primarily providing tested and supported distros, to integrated hardware solutions. This enables an extremely important aspect of the cloud native generation of computing – for the first time, you can practically move workloads between providers and platforms with virtually no change to the apps themselves.
This has long been a dream, as illustrated by Java, virtualization, and cloud IaaS, but not really practically possible in the past due to technical friction between different implementations. The Kubernetes ecosystem makes it possible to build and run an app on your laptop, move it directly to an on-premises test environment, and then move it to multiple different public cloud providers – without ever changing the app itself or having to ‘convert’ anything. That portability is transformational as organizations increasingly choose multi-cloud and hybrid cloud architectures.
Continued evidence that compute will be provided across a Continuum of Cloud Native options. Momentum around projects like Knative, Kata containers, and technologies like AWS Fargate and Azure Kubernetes Service virtual nodes illustrate that cloud native isn’t just about containers alone. Users have a variety of options for powering their apps and are choosing amongst them based on the needs and characteristics of each app. Not just the future, but the present, is about a continuum of options for running minimal, consistently packaged apps predictably, which is why we’ve built the Twistlock platform to support users across that entire set of options.
Follow us on Twitter
Follow us on Twitter for real time updates on the cloud native ecosystem, Twistlock product, and cloud native security threats.
How to Lock Down the Kernel to Secure the Container HostRead the Blog
One Chapter Ends, Another BeginsRead the Blog
The Greatest Security Risks Lurking in Your CI/CD PipelineRead the Blog
Cloud Platform Radar: Powerful Cloud Asset IdentificationRead the Blog
Securing Serverless Functions: Visibility with Serverless RadarRead the Blog