Ait/release 4.2

[chinameok]

Summary by CodeRabbit

• Documentation
  • Release notes updated to version 4.2.0 with Kubernetes 1.33 support.
  • Added ACP CLI and Hosted Control Plane (HCP) descriptions.
  • Introduced placeholders for Deprecated, Removed, Fixed Issues, and Known Issues sections.
  • Clarified network requirements and added a resources table (VIP, External IP, Domain, Certificate).
  • Wording updated in global cluster upgrade to reflect an "Upgrade" step for the service mesh.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Documentation updates: prerequisites rewrote Network guidance and added a structured Network Resources table; release notes bumped to 4.2.0 and added Features/Enhancements and placeholder sections; upgrade guide changed one heading from "Install" to "Upgrade" for Service Mesh Essentials.

Changes

Cohort / File(s)	Summary
Prerequisites and Network Configuration docs/en/install/prepare/prerequisites.mdx	Reworded Network section to neutral resource guidance and replaced narrative with a Network Resources table listing Global VIP, External IP, Domain Name, and Certificate with required/optional flags and descriptions.
Release Notes Update docs/en/overview/release_notes.mdx	Bumped version to 4.2.0; added Features/Enhancements entries (Kubernetes 1.33 support, ACP CLI, Hosted Control Plane) and inserted placeholder sections for Deprecated/Removed, Fixed Issues, and Known Issues.
Upgrade Instructions docs/en/upgrade/upgrade_global_cluster.mdx	Changed conditional step heading from "Install <Term name="company" /> Service Mesh Essentials" to "Upgrade <Term name="company" /> Service Mesh Essentials".

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Docs-only edits; check wording consistency and links in release notes.
• Verify the Network Resources table accuracy and required/optional flags.

Possibly related PRs

• Ait/release 4.2 #360 — Appears to contain identical docs changes to prerequisites, release notes, and upgrade files.
• doc: get upgrade instructions ready for 4.2.x #352 — Modifies upgrade docs (upgrade_global_cluster.mdx) in the same area.
• Ait 62503 #292 — Related edits to upgrade_global_cluster.mdx and Service Mesh wording.

Suggested reviewers

• youyongsong

Poem

🐰 I hopped through docs to tidy each line,

VIPs and IPs now sit in a fine table,
Version bumped, new features shine,
"Install" to "Upgrade" — a heading that's stable,
Hooray — small changes, made neat and able 🌿

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Ait/release 4.2' is vague and non-descriptive, using a branch name format rather than clearly summarizing the main changes.	Revise the title to clearly describe the primary changes, such as 'Release 4.2 with Kubernetes 1.33 support and ACP CLI' or similar to better communicate the changeset contents.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c42101a and 7b77f88.

📒 Files selected for processing (1)

• docs/en/overview/release_notes.mdx (1 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 61976dd and c42101a.

📒 Files selected for processing (3)

• docs/en/install/prepare/prerequisites.mdx (1 hunks)
• docs/en/overview/release_notes.mdx (1 hunks)
• docs/en/upgrade/upgrade_global_cluster.mdx (1 hunks)

🔇 Additional comments (5)

docs/en/upgrade/upgrade_global_cluster.mdx (1)

89-91: Terminology update correctly reflects upgrade context.

The change from "Install" to "Upgrade" is appropriate: within an upgrade procedure for the global cluster, users with existing Service Mesh v1 should upgrade (not reinstall) that component. The conditional marker aligns with the guard condition on line 91.

docs/en/install/prepare/prerequisites.mdx (2)

96-98: Network section guidance is clearer and more actionable.

The rewrite improves clarity by directly stating the requirement to prepare network resources, explicitly recommending hardware LoadBalancer when available, and noting the haproxy + keepalived alternative. This is more direct than the prior version.

---

102-137: New Network Resources table significantly improves documentation clarity.

Replacing unstructured text with a well-organized table (Resource | Mandatory | Quantity | Description) makes prerequisites more scannable and actionable. Descriptions appropriately contextualize each resource (e.g., high availability via load balancing, hybrid-cloud External IP, disaster recovery for domain name). The mandatory/optional flags are clear.

docs/en/overview/release_notes.mdx (2)

8-43: Feature descriptions are clear and well-structured.

The Kubernetes 1.33 and ACP CLI sections are concise and informative. The HCP section appropriately includes release status, lifecycle marker ("Asynchronous"), and key architectural benefits. External links are provided for each feature.

---

45-55: Placeholder sections should be completed or addressed before release.

The three sections (Deprecated and Removed Features, Fixed Issues, Known Issues) currently contain explicit "will be updated" and "under review" language. While appropriate for an in-progress PR, release notes should not ship with unfilled placeholder content, as users expect comprehensive information when consulting version-specific documentation.

Ensure these sections are populated before merging, or clarify the intended publication schedule if content will be added post-release.