Ambassador 0.50.1 available

We’re releasing Ambassador 0.50.1, a bug fix release to Ambassador 0.50. Ambassador 0.50.1 includes the following fixes:

• Defaults to only doing IPv4 DNS lookups. IPv6 can be enabled in the Ambassador module or in a Mapping. (#944)
• Fix spin loop where an invalid Envoy configuration would cause Ambassador to hang.
• Fix Docker support, so docker run and docker compose are supported. (#1160)
• Configuration from the filesystem is supported again; see the Running Ambassador documentation for details.
• Ambassador’s default YAML no longer requests permission for ConfigMaps (thanks to Patrick Sanders for pointing this out).

Installing 0.50.1

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

You can also install via Helm:

helm repo add datawire https://www.getambassador.io
helm upgrade --install --wait my-release datawire/ambassador

Upgrading to Ambassador 0.50.1

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

Onward

If you run into any problems with the update, please open an issue or join our Slack for some help.

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