News

Before the COVID-19 pandemic, enterprises were at various stages of their cloud strategies, whether that meant finally moving their email server to the cloud, switching to Microsoft 365, or even aggressively exiting their own data centers and going fully cloud-native.

Priyanka Sharma could be excused for feeling daunted when she became general manager of the Cloud Native Computing Foundation (CNCF) in June 2020. She’d been involved with the organization for years, but her assumption of the top role came at an unexpectedly difficult moment. The COVID-19 pandemic posed an existential threat to the CNCF’s popular KubeCon, an annual Kubernetes conference typically attended by tens of thousands of people. And that July, Google, a founding member of the CNCF, raised eyebrows when it decided not to transfer control of a state-of-the-art piece of open-source container technology called Istio to the foundation.

How does sportswear giant Adidas scale its operations? Three ways: technically, culturally and strategically. In this episode of The New Stack Makers podcast, Alex Williams, founder and publisher of The New Stack, speaks with Adidas Senior Director of Platform Engineering Iñaki Alzorriz, and Rastko Vukasinovic, Adidas’ director of solution architecture, on how the company scales its operations on Kubernetes.

Priyanka Sharma, Cloud Native Computing Foundation General Manager joined Yahoo Finance to discuss how to tackle the gender gap issue in the tech sector.

A press event at KubeCon EU looked at “What’s Next for Cloud Native.” Most interesting was the discussion on hybrid cloud and how open source will propel the future of edge computing.

As more and more applications are written (or refactored) and deployed in a cloud-native fashion, using containers and microservices, the concept of service meshes emerged to help admins and developers deal with the new complexity that accompanies this transition. Various service meshes have proliferated, and a big question now is whether the industry will standardize on a single service mesh platform like it standardized on Kubernetes as the go-to container orchestration platform.

As more and more applications are written (or refactored) and deployed in a cloud-native fashion, using containers and microservices, the concept of service meshes emerged to help admins and developers deal with the new complexity that accompanies this transition. Various service meshes have proliferated, and a big question now is whether the industry will standardize on a single service mesh platform like it standardized on Kubernetes as the go-to container orchestration platform.

A press event at KubeCon EU looked at “What’s Next for Cloud Native.” Most interesting was the discussion on hybrid cloud and how open source will propel the future of edge computing.

Big conferences always lead people to ask questions like “what is the key takeaway?” and this week’s KubeCon+CloudNativeCon Europe is no exception. Of course, it’s not necessarily true that there is one answer to this sort of question, and it certainly depends on who you ask. That guy you know who works for a storage vendor will inevitably quip that persistent storage, or some such thing, is still the biggest issue to tackle with Kubernetes, while the service mesh maintainer will talk to you about the great panel on proxies.

Virtual machine language WebAssembly (Wasm) is expanding into the purview of cloud native computing and is increasingly being integrated into Kubernetes environments.