docs: Add dedicated Iceberg compactor deployment guide for on-prem Kubernetes users

[Copilot]

The only mention of the dedicated compactor requirement for ENGINE = iceberg automatic maintenance was buried in the maintenance page behind a "contact us on Slack" call-to-action — no actionable deployment instructions existed for on-prem users.

Changes

• New page iceberg/deploy-iceberg-compactor.mdx: Covers why a compactor is required, Helm (compactorComponent) and Operator (spec.components.compactor.nodeGroups) YAML deployment examples, verification steps, and a sizing table by workload tier (light/medium/heavy).
• iceberg/maintenance.mdx: Replaced the Slack-redirect warning with a direct link to the new deployment page.
• iceberg/ov-internal.mdx: Added a <Note> in the compaction service section so the infrastructure requirement is visible at the overview level, not just on the maintenance page.
• docs.json: Registered the new page under the Internal Iceberg tables navigation group.

Related code PR

N/A

Related doc issue

https://github.com/risingwavelabs/risingwave-docs/issues/2376

Checklist

• I have run the documentation build locally to verify the updates are applied correctly.
• For new pages, I have updated mint.json to include the page in the table of contents.
• All links and references have been checked and are not broken.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add prerequisite documentation to deploy a dedicated Iceberg compactor when using internal iceberg (engine=iceberg)</issue_title>
<issue_description>When using engine=iceberg, is deploying a dedicated Iceberg compactor node still required?

Easy to Miss Infra Requirement in Doc
If so, this requirement is currently not documented in the Iceberg docs. The only place I see a note on it is in this document - https://docs.risingwave.com/iceberg/maintenance, but it is easy to miss, and instructs the user to contact the RW team on slack. It is also filed under table maintenance, which doesn't make sense for me if deploying a compactor is a prerequisite. Also, infrastructure deployment isn't really "table maintenance", though I understand the infrastructure component serves the purpose of maintaining tables through compaction.

Consider Adding or Adjusting Documentation to Give Instructions
We can adjust the documentation to have clean, useful instructions for on-prem deployment by adding another page or editing a section in quickstart or https://docs.risingwave.com/iceberg/ov-internal or both.

can we add a section that explains the following for on-prem users:

• Explains the need for a dedicated Iceberg compactor
• Provides guidance on configuring Kubernetes (Helm and Operator) to deploy it. Ideally including a code sample for yaml syntax that is used to do the deployment.
• Includes recommended sizing guidelines - teach the user how to determine how many iceberg compactors they will need and at what size

This will prevent misconfiguration and clarify deployment requirements for on-prem users.

Let me know if we still require a separate iceberg compactor and what you need for us to kick off this documentation improvement!

Thanks! </issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Add prerequisite documentation to deploy a dedicated Iceberg compactor when using internal iceberg (engine=iceberg) #1010

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.