From 2.13 to 2.26, 23 contributors submitted 51 commits for Apache APISIX. Thank you for your contributions to Apache APISIX.
Apache APISIX grew up as a community from the first day it was open-sourced, and quickly became the most active open-source API gateway project in the world. These achievements are inseparable from the joint efforts of community partners.
"If you want to go fast, go alone. If you want to go far, go together." The Apache APISIX Community Biweekly Report can help community members better grasp the progress of the Apache APISIX community so that everyone can participate in the Apache APISIX community.
We have also sorted out some issues for newcomers to the community to participate in! If you are interested, don't miss it!
Good First Issues
Description: Set validation on custom claims in OIDC auth, so that users can restrict access to the backend based on that rule.
Description: Add regression tests using
apisix:dev for APISIX Ingress to detect compatibility issues with the latest APISIX changes as early as possible.
Highlights of Recent Features
Recent Blog Recommendations
Accessing APISIX-Dashboard from Everywhere with Keycloak Authentication This guest blog describes how to setup an external access to apisix-dashboard protecting the URL with authentication managed by a keycloak server.
How to Integrate API Gateway and Consul? Not Consul K/V Apache APISIX supports the Consul service discovery registry. This article will walk you through the process of implementing service discovery and service registry in Apache APISIX.
Securing Admin Access to Apache APISIX In this short blog post, a couple of ways is listed to secure your Apache APISIX admin access.
A wealth of documentation tutorials and experience has been accumulated on the Apache APISIX official website and GitHub. If you encounter problems, you can look into the documentation, search keywords in the issues, or participate in the discussion on the issues, proposing your own ideas and practical experience.