[morningman]

Problem and change

The Kubernetes compute-storage decoupled deployment guide lists computeGroups.replicas but does not give users a complete scaling procedure. Add a linked scaling section to the compute-group configuration page in dev and 4.x, in English and Chinese. The requested scope is dev and 4.x only.

The guide covers adding/removing BE nodes, adding/removing complete compute groups, resource changes, FE scaling constraints, and completion checks. It explains Operator-managed BE decommission, the default non-decommission path and its image-dependent graceful flow, PVC cleanup during scale-in, and the different removal path when a whole compute-group entry is deleted.

Fixes #2370

Implementation evidence

Checked Doris branch-4.0, branch-4.1, and master, and the released Doris Operator 26.0.1 implementation rather than inferring behavior from the replica field:

• Operator's decommission option
• BE decommission and drop ordering
• Decommission completion check
• Whole-group removal and unused PVC cleanup
• Image capability detection and graceful scale-in
• FE replica/election constraints
• Doris 4.1 cloud BE removal and decommission operations

Validation and self-review

• git diff --check passed.
• Compiled all eight changed Markdown files with the Docusaurus Markdown processor; front matter and fenced YAML parse successfully, including the explicit scaling anchor.
• Checked new relative links and the scaling anchor across all four version/locale trees. The repository link linter reports 18 pre-existing missing anchors in the touched pages, all outside the added scaling instructions; no new internal-link errors were found.
• The i18n checker found both requested language/version pairs. It emits informational reminders about 3.x, which is outside the requested scope.
• Existing paths, navigation entries, and heading anchors are preserved. No site configuration or frontend code changes.
• No Kubernetes scaling test or full site build was run. The procedures and cautions are based on the pinned implementation above; they do not promise interruption-free scale-in.