release(aisix-cp): 0.2.0

[jarvis9443]

0.2.0 release sync of the public aisix-cp chart.

Bumps version and appVersion 0.1.0 → 0.2.0. appVersion pins the image tags, which now resolve to the published docker.io/api7/{aisix,aisix-cp-api,aisix-cp-dpm,aisix-cp-ui}:0.2.0.

Functional delta synced from the source-of-truth CP chart (control-plane/helm/aisix-cp):

• dp-manager /healthz liveness. Adds a plain-HTTP health listener (AISIX_DPMGR_HEALTH_LISTEN, default :7946) exposed as the health container port, with httpGet /healthz readiness + liveness probes. This probes outbox-poller liveness rather than the mTLS port 7944 (a kubelet cannot present a client cert, and a TCP check on 7944 stays green even if the poller is wedged): a stale poller now fails readiness (removed from the Service) and liveness (pod restarted). When dpm.service.healthListen="", the dp-manager serves no /healthz and the probes fall back to a TCP check on the mTLS port.

Public adaptations preserved (unchanged from 0.1.0): docker.io registries, empty image tag → .Chart.AppVersion, api.dpImage default → docker.io/api7/aisix:<appVersion>, and the chart README. README regenerated via helm-docs.

Merging publishes aisix-cp-0.2.0 to https://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: 10 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: 30d6b78e-e4f0-43c3-a2e5-e27455e244a7

📥 Commits

Reviewing files that changed from the base of the PR and between 0581107 and 246d4d3.

📒 Files selected for processing (4)

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-aisix-cp-0.2.0

---

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