Welcome to another hands-on Kuma guide! In the first guide, I walked you through securing an application using Kuma in a Kubernetes deployment. Since Kuma is platform-agnostic, I wanted to write a follow-up blog post on how to secure your application if you are not running in Kubernetes. This capability to run anywhere differentiates Kuma from many other service mesh solutions in the market.
Kong for Kubernetes (Kong for K8S) is a Kubernetes Ingress Controller based on the popular Kong Gateway open source project. Kong for K8S is fully Kubernetes Native and provides enhanced API management capabilities. From an architectural perspective, Kong for K8S consists of two parts: A Kubernetes controller, which manages the state of Kong for K8S ingress configuration, and the Kong Gateway which processes and manages incoming API requests.
As I look back at 2019 and all the amazing things we’ve achieved as a team, it was a big year for us at Kong. We’ve grown tremendously in just the past year alone, doubling to more than 160 employees, reaching 170 Kong Enterprise customers, hitting 100 million downloads of our open source Kong Gateway and running more than 1 million instances of Kong per month across the world.
Welcome to our second hands-on Kuma guide! The first one walked you through securing your application with mTLS using Kuma. Today, this guide will walk you through Kuma’s new L4 traffic routing rules. These rules will allow you to easily implement blue/green deployments and canary releases. In summary, Kuma will now alleviate the stress of deploying new versions and/or features into your service mesh. Let’s take a glimpse at how to achieve it in our sample application.
At KubeCon North America 2019, the community provided us with a ton of feedback and feature requests. We’re proud to release some of the most widely requested features in our latest version of Kuma: third-party CA (Certificate Authority) support, health checks, and a GUI! Kuma’s new health checks will help minimize the number of failed requests between your application. The third-party CA support will provide more flexibility when deciding how to secure your mesh.
As we approach the end of the year, I am reflecting on the fascinating evolution of how technology solves business problems. Since 2016, I have seen microservices drive buying decisions for many large enterprises. At the same time, open source adoption has been gaining ground from its emergence as a grassroots movement in the 90s to an industry-defining standard, driven by the rise of developers as strategic influencers.
Today, we’re thrilled to release Kuma 0.3, our open source control plane with brand new traffic routing capabilities. Kuma’s new L4 traffic routing rules allow you to easily implement blue/green deployments and canary releases. In summary, Kuma will now alleviate the stress of deploying new versions and/or features into your service mesh. Let’s take a glimpse at how to achieve it in our sample application: This sample application has three versions of the backend API.
At this year’s KubeCon, we debuted Kong for Kubernetes, the industry’s only fully Kubernetes-native ingress controller that supports end-to-end API management and is backed by an enterprise support subscription.
Today, we’re announcing an exciting, new partnership with codecentric AG, a leading IT consultancy based in Germany. Through Kong’s growing Go-To-Market (GTM) Partner Program, Codecentric will help German companies accelerate their transition to microservices by adopting Kong Enterprise.
We announced the release of Kuma – a modern, universal control plane for service mesh back in September 2019. Since then, a roaring wave of community feedback and contribution has flooded the project. And that’s a good thing, so thank you to everyone who has given their time to helping Kuma grow. One recurring feedback we got was that the community was excited to see a platform-agnostic service mesh.
