release(aisix): 0.9.0 by jarvis9443 · Pull Request #343 · api7/api7-helm-chart

jarvis9443 · 2026-08-13T09:51:10Z

Bumps aisix-cp and aisix to 0.9.0 (version + appVersion), so both charts pin the 0.9.0 images now published to docker.io/api7.

Synced from the control-plane chart

One functional delta accumulated this cycle: the cp-api startupProbe budget goes from 5 minutes to 30 (failureThreshold 60 → 360).

0.9.0 widens dpmgr_usage_events.request_id from uuid to text. A migration that rewrites a table is bounded by table size, not by a fixed bootstrap cost — measured at 6m21s on 10M rows, roughly what 30 days of retention holds at a sustained 4 req/s. cp-api runs the migration before it binds :8080, so the old 5-minute budget would have let liveness kill the pod mid-migration: exactly the crash loop this probe exists to prevent. The cost is that a genuinely wedged cp-api goes unrestarted for up to 30 minutes on first start only.

Preserved public adaptations

docker.io registries, empty image tags resolving to .Chart.AppVersion, the always-emit api.dpImage default, and the generated README.md files — all left divergent from the control-plane chart by design.

Verification

helm lint clean on both charts; rendered output resolves to docker.io/api7/aisix-cp-{api,dpm,ui}:0.9.0 and docker.io/api7/aisix:0.9.0, with the startupProbe rendering failureThreshold: 360.

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

Summary by CodeRabbit

New Features
- Released application and Helm charts as version 0.9.0.
- Improved startup handling to allow up to 30 minutes for initial migrations and scaling.
Documentation
- Updated chart documentation and version badges to reflect the 0.9.0 release.
- Added guidance about startup duration and first-start behavior.

Bumps both charts' version and appVersion to 0.8.2 and regenerates their READMEs. appVersion pins the image tags, which are published: docker.io/api7/aisix:0.8.2 and docker.io/api7/aisix-cp-{api,dpm,ui}:0.8.2. No template or values changes this cycle: the control-plane chart at the 0.8.2 release tree differs from this one only by the intended public adaptations (docker.io registries, empty tag and dpImage defaults resolving from appVersion, and this repo's README).

Bump aisix-cp and aisix to 0.9.0 (version + appVersion), so both charts pin the 0.9.0 images published to docker.io/api7. Syncs the one functional delta accumulated in the control-plane chart this cycle: the cp-api startupProbe budget goes from 5 minutes to 30 (failureThreshold 60 -> 360). 0.9.0 widens dpmgr_usage_events.request_id from uuid to text, and a migration that rewrites a table is bounded by table size rather than a fixed bootstrap cost — 6m21s measured on 10M rows. The old budget would have turned that upgrade into the crash loop the probe exists to prevent. Preserves the public adaptations: docker.io registries, empty image tags resolving to .Chart.AppVersion, the always-emit api.dpImage default, and the generated README files.

coderabbitai · 2026-08-13T09:51:23Z

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: 45 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: 5b6d70a3-00cf-40c0-867d-499b02606b1c

📥 Commits

Reviewing files that changed from the base of the PR and between bae876f and eabedf7.

📒 Files selected for processing (1)

charts/aisix-cp/README.md

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7f8c014b-9e4c-4c5f-b9a3-9d2e1e8164b7

📥 Commits

Reviewing files that changed from the base of the PR and between ac05cca and bae876f.

📒 Files selected for processing (5)

charts/aisix-cp/Chart.yaml
charts/aisix-cp/README.md
charts/aisix-cp/templates/api-deployment.yaml
charts/aisix/Chart.yaml
charts/aisix/README.md

📝 Walkthrough

Walkthrough

The AISIX Helm charts and README badges now use version 0.9.0. The API deployment startup probe allows up to 30 minutes for startup instead of 5 minutes.

Changes

AISIX release updates

Layer / File(s)	Summary
Chart release metadata `charts/aisix/Chart.yaml`, `charts/aisix/README.md`	Chart versions, application versions, and README badges update from `0.8.2` to `0.9.0`. The Control Plane README adds a horizontal separator after the Values table.
API startup probe window `charts/aisix-cp/templates/api-deployment.yaml`	The startup probe failure threshold increases from 60 to 360 checks. Comments document the 30-minute startup window and migration behavior.

Estimated code review effort: 2 (Simple) | ~10 minutes

Mergeability Score: ⚪ Minimal · up to bae87

This release updates chart versions and images and extends the cp-api startup budget for the documented 0.9.0 migration; no actionable merge-blocking risk remains beyond normal release validation.

Possibly related PRs

api7/api7-helm-chart#337: Updates the same AISIX chart release metadata.
api7/api7-helm-chart#338: Updates the same AISIX chart and README version metadata.
api7/api7-helm-chart#339: Updates AISIX chart versions and README badges.

Suggested reviewers: nic-6443

🚥 Pre-merge checks | ✅ 5 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
E2e Test Quality Review	⚠️ Warning	The PR changes cp-api startup behavior for a database migration, but adds no E2E tests; the repository has no test paths, and CI only lints these charts.	Add an E2E deployment test with a populated database that exercises the 0.9.0 migration, verifies API readiness, and detects restart or crash-loop failure.

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the AISIX 0.9.0 release, which matches the primary chart version updates.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Security Check	✅ Passed	The exact diff only changes chart versions, README badges, comments, and startupProbe failureThreshold; it adds no logs, responses, secrets, endpoints, permissions, ownership, TLS, or secret-refere...

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch release-aisix-0.9.0

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

# Conflicts: # charts/aisix-cp/Chart.yaml # charts/aisix-cp/README.md # charts/aisix/Chart.yaml # charts/aisix/README.md

The local helm-docs build emitted a trailing separator the repo's pinned version does not, failing the generated-docs check.

jarvis9443 added 2 commits August 11, 2026 13:23

jarvis9443 added 2 commits August 13, 2026 18:00

Merge remote-tracking branch 'origin/main' into release-aisix-0.9.0

bae876f

# Conflicts: # charts/aisix-cp/Chart.yaml # charts/aisix-cp/README.md # charts/aisix/Chart.yaml # charts/aisix/README.md

docs(chart): keep generated READMEs byte-identical to helm-docs output

eabedf7

The local helm-docs build emitted a trailing separator the repo's pinned version does not, failing the generated-docs check.

nic-6443 approved these changes Aug 13, 2026

View reviewed changes

jarvis9443 merged commit c966972 into main Aug 13, 2026
3 checks passed

jarvis9443 deleted the release-aisix-0.9.0 branch August 13, 2026 10:24

Navigation Menu

Uh oh!

release(aisix): 0.9.0 - #343

release(aisix): 0.9.0#343
jarvis9443 merged 4 commits into
mainfrom
release-aisix-0.9.0

jarvis9443 commented Aug 13, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented Aug 13, 2026 •

edited

Loading

Review limit reached

Walkthrough

Changes

❌ Failed checks (1 warning)

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

jarvis9443 commented Aug 13, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Synced from the control-plane chart

Preserved public adaptations

Verification

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Aug 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review limit reached

Walkthrough

Changes

❌ Failed checks (1 warning)

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

jarvis9443 commented Aug 13, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Aug 13, 2026 •

edited

Loading