4 open source lessons for 2021
2020 fundamentally changed how many companies and teams work—seemingly overnight, remote-first cultures became the new norm and people had to change how they communicate and collaborate.
2020 fundamentally changed how many companies and teams work—seemingly overnight, remote-first cultures became the new norm and people had to change how they communicate and collaborate.
Managing Kubernetes clusters is hard. Managing Kubernetes clusters at scale across a variety of infrastructures is—well—even harder. The Kubernetes community project Cluster API (CAPI) enables users to manage fleets of clusters across multiple infrastructure providers.
Overview One of the hallmarks of “the edge” in computing is the array of sensors, controllers, and microcontroller unit (MCU) class devices that produce data and perform actions. For Kubernetes to be a versatile edge computing solution, a cluster needs to easily find these leaf devices.
J4K is a developer-oriented conference focused on open source and hybrid cloud application development of Java and Kubernetes. This is a community event, delivered by stellar Java community leaders, and is dedicated to enriching developers and architects with cloud-focused solutions. Registration is free.
Dapr integration in the Azure API Management (APIM) service is now available. This new capability enables operations teams to directly expose Dapr microservices as APIs and make those APIs discoverable and easily consumable by developers with proper controls across multiple Dapr deployments—whether in the cloud, on-premises, or on the edge.
We’re excited to announce a new extension for Azure Functions that lets a function seamlessly interact with Dapr for building cloud-native applications. Azure Functions provides an event-driven programming model and Dapr provides a set of essential cloud-native building blocks.
A Kubernetes cluster requires compute resources to run applications and these resources may need to increase or decrease depending on the application requirements. This typically falls under the category of “scaling” and can be broadly divided into cluster and application scaling.
Thinking about joining the Kubernetes Release Team? Curious what it even is? As someone who started as a shadow on the Communications team for the 1.16 and 1.17 Release Team and eventually became the Communications Lead for the 1.18 release, I want to share what I’ve learned from this journey and answer any questions you may have about the Release Team.
Last year Microsoft and Red Hat announced Kubernetes Event-driven Autoscaling (KEDA) – a way to bring event scale for any container or workload deployed into any Kubernetes cluster. Since then, we have been blown away by the response from the community in helping to make KEDA even better.
As more users take advantage of Kubernetes for their Windows applications, the Windows community in Kubernetes has been working on improvements that enable even more use cases. With the release of Kubernetes v1.18, many of these changes are taking shape.
The questions started around KubeCon San Diego. Maybe because we had just released Helm 3. Or, maybe because a few operator tools had been put up for adoption by CNCF. Whatever the cause, I started receiving questions about Helm and operators.
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.