Highlight
New APISIX standalone backend
Benefiting from the API-driven standalone mode (enhancements sponsored by API7) released in APISIX 3.13, ADC has introduced a new backend for Ingress Controller support.
The new apisix-standalone backend, which is isomorphic to any other backend, ensures that users do not need to provide different configuration inputs for different scenarios, but rather use a single unified configuration for multiple different gateway products.
Input configurations will be converted on a best-effort basis to the configuration/API calls required by the specified backend.
With this new ADC backend, APISIX in Kubernetes will have the opportunity to become a truly stateless API gateway with no etcd and no persistence.
ADC is already used as a core by the API7 Ingress Controller and will further enhance the capabilities of the APISIX Ingress Controller. ADC has become an important part of the API7 portfolio, bringing value to a wider range of products and users..
What's Changed
- feat(apisix-standalone): add new experimental backend by @bzp2010 in #269
- fix(apisix-standalone): incorrect desc field in service inlined upstream by @bzp2010 in #276
- fix(apisix-standalone): remove path_prefix and strip_path_prefix by @bzp2010 in #277
- fix(apisix-standalone): remove zod-based transformer by @bzp2010 in #280
- fix(apisix-standalone): consumer sync exception by @bzp2010 in #282
- fix(apisix-standalone): credential modifiedIndex is not updated by @bzp2010 in #288
- fix(apisix): transform upstream nodes to array by @bzp2010 in #290
- chore(apisix): remove experimental log by @bzp2010 in #292
- feat: bump to 0.20.0 by @bzp2010 in #293
Full Changelog: v0.19.1...v0.20.0