From 11.15 to 11.30, 37 contributors submitted 87 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 #5451​

Link: https://github.com/apache//issues/5451

Issue description:

Nginx comes with a response content replacement library that can replace partial content: http://nginx.org/en/docs/http/ngx_http_sub_module.html

sub_filter '

There is a library that supports regular substitution (as I remember Openresty already supports it by default): ngx_http_substitutions_filter_module, which can replace content with regular expressions: ngx_http_substitutions_filter_module

subs_filter_types text/html text/css text/xml;subs_filter st(\d*).example.com $1.example.com ir;subs_filter a.example.com s.example.com;subs_filter http://$host https://$host;

However, it seems that 's response-rewrite plugin only supports full replacement, which is equivalent to directly replacing all responses with the return set by the plugin, and does not support partial content replacement:

curl http://127.0.0.1:9080//admin/routes/1  -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '{    "methods": ["GET"],    "uri": "/test/index.html",    "plugins": {        "response-rewrite": {            "body": "{\"code\":\"ok\",\"message\":\"new json body\"}",            "headers": {                "X-Server-id": 3,                "X-Server-status": "on",                "X-Server-balancer_addr": "$balancer_ip:$balancer_port"            },            "vars":[                [ "status","==","200" ]            ]        }    },    "upstream": {        "type": "roundrobin",        "nodes": {            "127.0.0.1:80": 1        }    }}'

Does this plugin support partial replacement or regular replacement? If not, is there any other solution for ?

Issue #5647​

Link: https://github.com/apache//issues/5647

Issue description:

The current documentation provides a way to install directly using RPM on CentOS7, but the current has switched its dependency to -base version without providing its RPM installation method, which will cause the installation to fail.

Is it possible to add the command for installing the RPM for -base.

Highlights of Recent Features​

• kafka-logger supports logging request body（Contributor: windyrjc）

• New <a href="/technews/tag_37.html" style="color: #333;" target="_blank" class="inner-tag">azure-functions plugin, seamlessly integrated with Azure Serverless Function（Contributor: bisakhmondal）

• The WASM plugin supports running in the header_filter phase（Contributor: spacewander）

• New google-cloud-logging plugin for pushing logs to Google Cloud logging Service（Contributor: shuaijinchao）

• New openwhisk plugin, integrated with Apache OpenWhisk serverless platform（Contributor: bzp2010）

• kafka-logger and http support logging response bodies（Contributor: dmsolr）

• Enriched mTLS support in Ingress for HTTPS and gRPCs type upstream（Contributor: nic-6443）

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.

Recent Blog Recommendations​

• Using Apache Ingress Gateway to access Custom Monitoring in KubeSphere：

  This article will take Apache Ingress Controller as an example to show you in detail how to quickly use different types of gateways and status monitoring for Kubernetes clusters through KubeSphere.

• Contributer to Committer journey @Apache ：

  In this article, Shivam Singh (@1502shivam-singh) gives a brief of his journey from starting out in the Apache community, from a contributor to an Apache member and committer. His journey can help other people looking to startup in the Apache community or Open Source in general.

• Developing Ingress Controller with Nocalhost in Kubernetes：

  This article walks you through using Nocalhost to seamlessly connect your local development machine to a remote Kubernetes cluster, allowing you to use IDE to develop and debug Apache Ingress Controller. Giving you the ability to comfortably develop and debug your remote apps with your existing skills.

• Apache embraces the WASM ecosystem：

  Support for WASM will be added in the upcoming Apache version (2.11.0)! By reading this article you will learn how Apache deploys the support and development of this feature from 0 to 1.

• How to integrate with Dapr to build Apache Gateway Controller：

  This article will show you how to create an Apache controller by integrating Dapr, includes the concept of the project and the specific operation steps.