add some detail about envoy-gateway-operator

[woodgear]

Summary by CodeRabbit

• Documentation
  • Added a new subsection on adding taint tolerations to the operator with a CLI patch example
  • Expanded operator status verification with pod-listing and Running-state checks
  • Reworked UI installation flow: switch to global cluster, locate/install GatewayAPI plugin, and updated step ordering
  • Cleaned up installation guidance and adjusted subsequent steps for clarity

[coderabbitai]

Walkthrough

Updates the Envoy Gateway Operator and UI installation docs: adds a "How to Add Taint Tolerations to the Operator" subsection with a kubectl patch, adds operator pod status verification, and reorganizes UI installation steps to require switching to the global cluster and installing the GatewayAPI Plugin.

Changes

Cohort / File(s)	Summary
Documentation Update docs/en/solutions/How_to_Install_EnvoyGatewayOperator_And_UI_Before_ACP_4.2.md	Adds a subsection for taint tolerations (kubectl patch), adds operator status verification snippet (listing operator pods and checking Running state), reorders UI installation steps to include "Switch to global cluster" and explicit install of the Alauda Container Platform GatewayAPI Plugin; removes prior Step 2–3 flow and adjusts subsequent steps.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• add envoy-gateway install solutions #92: Modifies the same EnvoyGatewayOperator/UI installation document and appears directly related to these doc updates.

Suggested reviewers

• tyzhou111

Poem

🐰 I hopped through guides, made steps neat and light,
I added tolerations, now pods sleep at night,
A status check here, a cluster switch there,
Plugin installed — deployment hums in the air! 🥕

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'add some detail about envoy-gateway-operator' is vague and uses generic phrasing that doesn't convey the specific nature of the additions.	Use a more specific title that highlights the main changes, such as 'Add taint toleration config and update GatewayAPI UI installation steps for Envoy Gateway Operator' to better reflect the actual content additions.

✅ 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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

🤖 Fix all issues with AI agents

In
`@docs/en/solutions/How_to_Install_EnvoyGatewayOperator_And_UI_Before_ACP_4.2.md`:
- Line 74: The heading "###### How to Check the Operator Status**" has an extra
trailing bold marker; edit the heading text (the line containing "###### How to
Check the Operator Status**") to remove the stray "**" so it becomes "###### How
to Check the Operator Status" (or wrap the entire heading properly with matching
bold/heading markers if intended), ensuring the markdown heading renders
correctly.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In
`@docs/en/solutions/How_to_Install_EnvoyGatewayOperator_And_UI_Before_ACP_4.2.md`:
- Around line 58-72: Add a caution and a scoped example around the kubectl patch
that sets tolerations so readers aren’t advised to use the overly-broad
"operator: Exists" alone; update the section that shows the patch (the
tolerations JSON under the patch command) to include a brief warning sentence
and an alternative scoped toleration example using "key" (e.g.,
"node-role.kubernetes.io/control-plane") and "effect" ("NoSchedule") alongside
"operator": "Exists" so the toleration targets specific taints instead of all
taints.