release(aisix): 0.7.1

[jarvis9443]

Releases aisix-cp and aisix 0.7.1. Both charts move together, since appVersion pins the image tag on each side and a control plane and data plane from different releases is not a combination we ship.

Version bump

version and appVersion to 0.7.1 on both charts, and regenerated READMEs. The images the new appVersion resolves to are published: docker.io/api7/aisix:0.7.1 and docker.io/api7/aisix-cp-{api,dpm,ui}:0.7.1.

Synced delta (aisix-cp)

One functional change accumulated in the control-plane source chart since 0.7.0: dp-manager now receives AISIX_DPMGR_BASE_URL, gated on api.dpmgrBaseURL being set. It seeds the subject alternative names of the TLS server certificate dp-manager presents, so a data plane that dials the control plane by IP address can complete the handshake. Without this the value reached only cp-api, which bakes it into the generated install snippet, and a remote data plane addressed by IP looped forever on certificate not valid for name.

The values.yaml comment on api.dpmgrBaseURL is synced along with it; the key itself already existed.

Preserved public adaptations

The sync leaves the public chart's intentional divergences intact: docker.io registries, empty image tags defaulting to .Chart.AppVersion, the always-emitted api.dpImage default, and the generated README.md. After this change the only remaining diff against the control-plane source chart is exactly that set.

Data-plane chart

charts/aisix is authored here and has no source chart to sync from, so it takes the version and appVersion bump only.

Verification

helm lint passes on both charts. Rendering aisix-cp resolves every image to docker.io/api7/aisix-cp-*:0.7.1 and AISIX_CLOUD_DP_IMAGE to docker.io/api7/aisix:0.7.1; the new environment variable renders when api.dpmgrBaseURL is set and is absent when it is not. Rendering aisix resolves the gateway image to docker.io/api7/aisix:0.7.1.

Merging publishes aisix-cp-0.7.1 and aisix-0.7.1 to charts.api7.ai.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 57 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e1c808ad-a23f-4047-9f65-c8f695e0b021

📥 Commits

Reviewing files that changed from the base of the PR and between d146ee1 and 0c36f44.

📒 Files selected for processing (6)

• charts/aisix-cp/Chart.yaml
• charts/aisix-cp/README.md
• charts/aisix-cp/templates/dpm-deployment.yaml
• charts/aisix-cp/values.yaml
• charts/aisix/Chart.yaml
• charts/aisix/README.md

---

_{Comment @coderabbitai help to get the list of available commands.}