From Jun 16th to Jun 30th, 29 contributors submitted 98 commits for Apache . Thank you all for your contributions to Apache . It is your selfless contribution to make the Apache project better!
Introduction
Apache has grown as a community from the first day of open source and has quickly become the most active open source API gateway project in the world. These achievements cannot be achieved without the joint efforts of our community partners.
"If you want to go fast, go alone.If you want to go far, go together." The Apache Community Weekly Report hopes to help community members better understand the weekly progress of the Apache community and and facilitate everyone to participate in the Apache community.
We have also compiled some issues suitable for newcomers to the community to participate in! If you are interested, don't miss it!
Contributor Statistics
Good first issue
Issue #1075
Link: https://github.com/apache/-ingress-controller/issues/1075
Description: Currently, we will use the latest version of for e2e testing to ensure the compatibility of Ingress and .
But we don't know about some of the latest changes in . I suggest we add a scheduled job to use :dev image for regression testing.
We used to use :dev for e2e testing by default, but this way would affect our development experience, and sometimes we found that e2e failed, but it was actually just due to some changes in .
Highlights of Recent Features
Export some importent params for kafka-client（Contributor: mikawudi）
Allow users to specify plugin execution priority（Contributor: tzssangglass）
Support for checking the plugin_metadata in the configuration file（Contributor: fesily）
Recent Blog Recommendations
- Getting Started with Test Cases
This article mainly introduces how to write test cases for Apache API Gateway.
- integrates with Ory Hydra
This article describes how Apache integrates with Ory Hydra to implement centralized authentication.
- Use Keycloak with API Gateway to secure APIs
This article describes how Apache integrates with Keycloak (OpenID Connect Provider) to secure your APIs.
The Apache project website and the Github issue have accumulated a wealth of documentation and experience, so if you encounter problems, you can read the documentation, search the issue with keywords, or participate in the discussion on the issue to put forward your own ideas and practical experience.