For Microsoft’s internal teams and external customers, we store datasets that span from a few GBs to 100s of PBs in our data lake. The scope of analytics on these datasets ranges from traditional batch-style queries (e.g., OLAP) to explorative ”finding the needle in a haystack” type of queries (e.g., point-lookups, summarization).
Today, we’re announcing Azure Service Operator―an open source project we’ve been working on in collaboration with a handful of customers to expose several Microsoft Azure services as Kubernetes operators. As we’ve seen Kubernetes adoption grow exponentially, we’ve also seen an increasing desire from customers to manage their resources exclusively through the Kubernetes control plane.
On behalf of HashiCorp and Microsoft, I am excited to announce the release of Azure DevOps Provider 0.0.1 for Terraform. With this provider, you will be able to manage Azure DevOps resources like projects, CI/CD pipelines, and build policies through Terraform.
The Distributed Application Runtime (Dapr) project is growing rapidly are we’re grateful for all the community support and customer feedback. While working with customers building business applications, we find that one of the most frequent needs is the ability to schedule, automate, and orchestrate business processes. This is often called a business workflow.
The code for a new open source differential privacy platform is now live on GitHub. The project is jointly developed by Microsoft and Harvard’s Institute for Quantitative Social Science (IQSS) and the School of Engineering and Applied Sciences (SEAS) as part of the OpenDP initiative.
The Open Compute Project (OCP) Global Summit, kicking off virtually on May 12, is where a vibrant and growing community will come together to help grow, drive, and support the open hardware ecosystem.
Yesterday, Helm became a graduated project in the Cloud Native Computing Foundation (CNCF), joining a select group of projects that the CNCF recognizes for achieving majority adoption by the cloud-native community.
Since the October 2019 announcement of the Distributed Application Runtime (Dapr), we have seen a tremendous response and the emergence of an engaged Dapr community.
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.
Linux container technology has changed the face of computing, but especially distributed computing in publicly rentable servers commonly said to be “the public cloud” (like Microsoft Azure). With containers came tooling – like Docker – and systems that orchestrate potentially millions of them – with Kubernetes becoming the most widely used.
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.
