Doomsday?!

[c0c0n3]

Hear ye, hear ye! His Majesty Istio I.V commands all our loving subjects whatsoever to discover and apprehend Sir Adapter Boost, Baronet, to carry him before the Chief Magistrate of the country, town or place where he shall be apprehended. Sir Adapter Boost shall be hanged, drawn and quartered!
God save the King!

Joking aside, Istio 1.5 got released yesterday (5 Mar 2020) and apparently they're going to ditch the whole Mixer/Adapter ecosystem:

Mixer is deprecated. The functionality provided by Mixer is being moved into the Envoy proxies. Use of Mixer with Istio will only be supported through the 1.7 release of Istio.

See deprecation warnings on:

• https://istio.io/docs/reference/config/policy-and-telemetry/
• https://istio.io/docs/reference/config/policy-and-telemetry/adapters/

Also the adapter dev guide hasn't been updated with a migration path or anything related to deprecation:

• https://github.com/istio/istio/wiki/Mixer-Out-Of-Process-Adapter-Dev-Guide

Given the fast-paced release cycle, 1.7 is likely to be released before the end of the year. Where does that leave us? Are we going to deliver something that in practice will never be used?

One option would be to still use an Istio mesh but deploy our own sidecar instead, but we need to discuss a way forward.

[c0c0n3]

It looks like the "new" way of doing things is through WASM plugins

• https://istio.io/docs/concepts/wasm/

Except, this is still alpha and a bit of a moving target

We’re not quite ready to make this setup the default, given that we consider Wasm support to be Alpha

https://istio.io/blog/2020/wasm-announce/ (post dated 5 Mar 2020)