Knative & Linkerd Support, JSON logging, and more in Ambassador 0.73

Knative & Linkerd Support, JSON logging, and more in Ambassador 0.73

  • August 3, 2019
Table of Contents

Knative & Linkerd Support, JSON logging, and more in Ambassador 0.73

We’re releasing Ambassador 0.73 today, with native support for the Linkerd 2.0 service mesh and the Knative serverless platform. Ambassador focuses on the ingress (“north-south”) use case for traffic management within modern cloud-native applications, and accordingly we’ve had integrations for quite some time with service meshes that focus on the service-to-service (“east-west”) use cases, such as Istio, Consul, and Linkerd. At the recent KubeCon EU, we saw an increased amount of interest around Linkerd, and also some potentially avoidable friction with the integration, and so we’ve improved the operator experience around this (more details below).

Source: getambassador.io

Share :
comments powered by Disqus

Related Posts

Ambassador and the Cloud Native Ecosystem—Part 1: Monitoring

Ambassador and the Cloud Native Ecosystem—Part 1: Monitoring

In a Cloud Native world, microservices are running with ephemeral containers that are regularly deployed to multiple availability zones, regions, and even multiple clouds. As these cloud native applications become more complex, our supporting solutions like monitoring, have also had to become more complex. Today, more traditional monitoring responsibilities are being automated, and monitoring has become less human centric.

Read More
Rate Limiting at the Edge

Rate Limiting at the Edge

I’m sure many of you have heard of the “Death Star Security” model—the hardening of the perimeter, without much attention paid to the inner core—and while this is generally considered bad form in the current cloud native landscape, there is still many things that do need to be implemented at edge in order to provide both operational and business logic support. One of these things is rate limiting. Modern applications and APIs can experience a burst of traffic over a short time period, for both good and bad reasons, but this needs to be managed well if your business model relies upon the successful completion of requests by paying customers.

Read More