Empowering cloud-native developers on Kubernetes anywhere
Hello KubeCon and welcome to San Diego! It’s fantastic to have the chance to get some warm California sun, as well as the warmth of the broader Kubernetes community.
Hello KubeCon and welcome to San Diego! It’s fantastic to have the chance to get some warm California sun, as well as the warmth of the broader Kubernetes community.
Event-driven applications are a key pattern for cloud-native applications. Event-driven is at the core of many growing trends, including serverless compute like Azure Functions. Event-driven means your application responds and reacts to different events – business or system events.
Next week is KubeCon North America 2019, but we wanted to give you an early preview of one of the things we’ll be showing. Over the last few years, we’ve been working on tools for the cloud native ecosystem. From Helm and Brigade to Porter and Rudr, each tool we have built is designed to stand on its own.
Ecosystem complexity increases every time we look around, our dizzying panoply of choices multiplies by the day, and (now, as always) we need a way to find, share, and operate applications reliably, in production, and at scale. What’s a busy Kubernetes user to do? Helm is the well-known and much-used package manager for Kubernetes.
Last year at Microsoft Connect and DockerCon we announced the Cloud Native Application Bundle (CNAB) specification in partnership with Docker, HashiCorp, and Bitnami. Since then the CNAB community has grown to include Pivotal, Intel, Datadog, and others, and we are all extremely pleased to announce that the CNAB core 1.
Modern application infrastructure is being transformed by containers. The question is: How do you get started? Understanding what problems containers, Docker, and Kubernetes solve is essential if you want to build modern cloud-native apps or if you want to modernize your existing legacy applications.
I’m a developer and I’ll admit it, I’m learning Kubernetes. I’ve been developing web applications now for more than 20 years; however, the past two years I’ve moved to working with microservices applications. Originally the microservices were web sites on multiple virtual machines.
Today we are excited to launch Service Mesh Interface (SMI) which defines a set of common, portable APIs that provide developers with interoperability across different service mesh technologies including Istio, Linkerd, and Consul Connect. SMI is an open project started in partnership with Microsoft, Linkerd, HashiCorp, Solo.
Helm is the best way to find, share, and use software built for Kubernetes, and the eagerly anticipated Helm 3 alpha is now available for testing. Try it out, give feedback, and help the Helm community get it ready for you to depend upon.
Greetings and welcome to KubeCon EU in Barcelona! As always, it is wonderful to see the community come together to celebrate how Kubernetes has made cloud-native ubiquitous and changed the way that we build and manage our software.
Event-driven architectures are a natural evolution of microservices, enabling a flexible and decoupled design, and are increasingly being adopted by enterprise customers. Fully managed serverless offerings like Azure Functions are event–driven by design, but we have been hearing from customers about gaps in these capabilities for solutions based on Kubernetes. Scaling in Kubernetes is reactive, based on the CPU and memory consumption of a container.
Microservices built on Kubernetes are fast becoming one of the core scenarios where computing is done, and Kubernetes development and operations skills are therefore becoming a larger part of any cloud-native toolset.
The service mesh may sound complex, but at its heart, it’s a very simple idea: a set of network proxies that transparently run alongside microservices, implementing reliability, observability, and security features by measuring and manipulating inter-service (“east-west”) traffic.