emissary-ingress/emissary v3.1.0

Emissary Ingress 3.1.0

on GitHub

🎉 Emissary Ingress 3.1.0 🎉

Emissary Ingress is an open source, Kubernetes-native microservices API gateway built on the Envoy Proxy.

Upgrade Emissary - https://www.getambassador.io/reference/upgrading.html
View changelog - https://github.com/emissary-ingress/emissary/blob/v3.1.0/CHANGELOG.md
Get started with Emissary on Kubernetes - https://www.getambassador.io/user-guide/getting-started

• Feature: The agent is now able to parse api contracts using swagger 2, and to convert them to
  OpenAPI 3, making them available for use in the dev portal.

• Feature: Adds a new command to the agent directive service to manage secrets. This allows a third
  party product to manage CRDs that depend upon a secret.

• Feature: Add additional pprof endpoints to allow for profiling Emissary-ingress:

  • CPU profiles
    (/debug/pprof/profile)
  • tracing (/debug/pprof/trace)
  • command line running
    (/debug/pprof/cmdline)
  • program counters (/debug/pprof/symbol)

• Change: In the standard published .yaml files, the Module resource enables serving remote
  client requests to the :8877/ambassador/v0/diag/ endpoint. The associated Helm chart release
  also now enables it by default.

• Bugfix: A regression was introduced in 2.3.0 causing the agent to miss some of the metrics coming
  from emissary ingress before sending them to Ambassador cloud. This issue has been resolved to
  ensure that all the nodes composing the emissary ingress cluster are reporting properly.

• Security: Updated Golang to 1.17.12 to address the CVEs: CVE-2022-23806, CVE-2022-28327,
  CVE-2022-24675, CVE-2022-24921, CVE-2022-23772.

• Security: Updated Curl to 7.80.0-r2 to address the CVEs: CVE-2022-32207, CVE-2022-27782,
  CVE-2022-27781, CVE-2022-27780.

• Security: Updated openSSL-dev to 1.1.1q-r0 to address CVE-2022-2097.

• Security: Updated ncurses to 1.1.1q-r0 to address CVE-2022-29458