AMBASSADOR FEATURE RELEASE

Ambassador Ingress Controller, better config reporting, updated Envoy Proxy

Ambassador 0.80 is now generally available

We’re releasing Ambassador 0.80 today, a feature release for Ambassador. 0.80 includes:

• Support for Ingress resources, making Ambassador an official ingress controller.
• Basic configuration health reporting in diagnostics. Ambassador will now report certain types of broken configuration in the diagnostics UI to enable easier troubleshooting.
• Envoy no longer crashes when an AuthService is updated while under load.

Kubernetes Ingress support

The Kubernetes Ingress specification has a long history. In early 2019, after many years in beta, the specification was officially finalized. With the specification finalized, we’re officially supporting the Ingress resource. The motivation for supporting Ingress is twofold:

• Some ecosystem tools rely on Ingress as a common interface, and we want to work with them.
• We want to make it easier for users who are migrating from other ingress controllers to try Ambassador.

So, given that we now support Ingress, how do we expect Ambassador configuration to evolve? Going forward, we expect:

• For most users, the Ambassador CRDs should be used for configuration.
• If you need to integrate with other tools that rely on Ingress or have existing Ingress resources, Ambassador will support reading these as well.

Note that we do not expect to deprecate any of the existing methods any time soon (e.g., annotations). We do want to continue to simplify the user experience and create a clear, understandable user model. For more details on the ingress support, we’ve added documentation on ingress resources and Ambassador. (And if you have feedback, please hop on the Slack and let us know.)

Installing 0.80

0.80 is available with the Docker tag quay.io/datawire/ambassador:0.80.0. Update your existing deployment manifest with this tag and kubectl applyto install 0.80 into your cluster.

You can also install via Helm:

helm install stable/ambassador

Upgrading

Ambassador relies on Kubernetes deployments for updates. To update Ambassador, change your Kubernetes manifest to point to quay.io/datawire/ambassador:0.80.0 and run kubectl apply on the updated manifest. Kubernetes will apply a rolling update and update to 0.78.

Get Involved

If you run into any problems with the update, please open an issue or join our Slack for some help. In addition, Ambassador Pro provides integrated authentication, rate limiting, commercial support, and more. If you’re interested, please contact us.

And, if Ambassador is working well for you, we’d love to hear about it. Drop us a line in the comments below, or @ambassadorlabs on Twitter.