release(aisix): 0.7.0 - #329
Conversation
Bump both charts to 0.7.0. appVersion pins the published
docker.io/api7/aisix-cp-{api,dpm,ui}:0.7.0 and docker.io/api7/aisix:0.7.0 images.
aisix-cp carries no functional delta this cycle — the control-plane
source-of-truth chart was unchanged since 0.6.0, so this is a version
bump plus the regenerated README. The public adaptations (docker.io
registries, empty tag defaulting to appVersion, dpImage defaulting to
docker.io/api7/aisix:<appVersion>, README) are preserved.
aisix moves its readiness probe from /status/ready on the metrics
listener to /readyz on the proxy listener. /readyz used to withdraw an
instance whose configuration watch had gone five minutes without an
event, which an idle environment does routinely, so every replica left
the Service while healthy. api7/aisix#841 removed that condition and
ships in appVersion 0.7.0, so readiness can go back to the listener
that actually carries the traffic.
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 19 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
Comment |
2 participants
Releases the
aisix-cp(control plane) andaisix(data plane) charts at 0.7.0. Both carry the sameversionandappVersion, andappVersionpins the images published for this release:docker.io/api7/aisix-cp-{api,dpm,ui}:0.7.0anddocker.io/api7/aisix:0.7.0.aisix-cp
Version bump plus the regenerated README, nothing else. The control-plane source-of-truth chart saw no changes this cycle, so there is no functional delta to sync. The public adaptations are preserved:
docker.ioregistries, an emptytagresolving to.Chart.AppVersion,api.dpImagedefaulting todocker.io/api7/aisix:<appVersion>, and the README.aisix
Version bump, plus the readiness probe moves from
/status/readyon the metrics listener to/readyzon the proxy listener./readyzpreviously returned 503 once the configuration watch had gone five minutes without an event. That measures elapsed time since the last configuration event, which an environment whose resources are not changing does not produce — so every replica crossed the threshold simultaneously and the Service lost all its endpoints while perfectly healthy. The chart worked around it by probing/status/readyon the metrics port instead. api7/aisix#841 removed that condition and ships in appVersion 0.7.0, so readiness returns to the listener that actually carries the traffic.Verified with
helm lintandhelm templateon both charts: the three control-plane images andAISIX_CLOUD_DP_IMAGEresolve todocker.io/...:0.7.0, and the data-plane probe renders as/readyzonproxy.Merging publishes
aisix-cp-0.7.0andaisix-0.7.0to charts.api7.ai.