Add HCS VIP LoadBalancer Service docs#155
Conversation
|
Important Review skippedToo many files! This PR contains 202 files, which is 52 over the limit of 150. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (11)
📒 Files selected for processing (202)
You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughAdds English and Chinese solution guides describing how to use Huawei HCS precreated external VIPs with Kubernetes LoadBalancer Services (ACP 4.2). Documents prerequisites, steps to enable kube-proxy IPVS mode, creating MetalLB/ACP External IP Pools, Service annotation usage, and verification commands. Changes
Sequence Diagram(s)sequenceDiagram
participant Client as External Client
participant VIP as HCS VIP (platform LB)
participant VM as HCS VM Layer / Hypervisor
participant Node as Cluster Node (kube-proxy IPVS)
participant Pod as Backend Pod
participant MetalLB as MetalLB / ACP External IP Pool
Note over MetalLB,VIP: Setup
MetalLB->>VIP: Allocate VIP from External IP Pool
Note over Client,Pod: Runtime traffic flow
Client->>VIP: TCP:S connect to VIP:port
VIP->>VM: Route to assigned HCS VM / NIC
VM->>Node: Forward to cluster node owning VIP
Node->>Node: kube-proxy (IPVS) lookup for Service
Node->>Pod: Forward traffic to selected Pod endpoint
Pod-->>Client: Response (reverse path via Node/VM/VIP)
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/zh/solutions/How_to_Use_HCS_VIP_for_LoadBalancer_Service_in_HCS.md`:
- Around line 25-46: Add a language tag to the fenced code block that contains
the ASCII architecture diagram so Markdown lint MD040 is satisfied: locate the
triple-backtick fence that opens the diagram (the ASCII art block starting with
"外部客户端") and change the opening fence from ``` to ```text (i.e., add the
language identifier "text") so the diagram block is recognized properly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 71f4594f-9bb6-436c-ae6d-6aa6cb49016f
📒 Files selected for processing (2)
docs/en/solutions/How_to_Use_HCS_VIP_for_LoadBalancer_Service_in_HCS.mddocs/zh/solutions/How_to_Use_HCS_VIP_for_LoadBalancer_Service_in_HCS.md
* feat:add migrate harbor registry pvc storage to s3. * docs: update migration guide for Harbor registry PVC storage to S3, clarifying steps and improving formatting
* Create Kafka_Scale_Switching.md * Update Kafka_Scale_Switching.md * Update Kafka_Scale_Switching.md * Update Kafka_Scale_Switching.md
* add docing not standard tpl * add docking non standard oidc * estructure OIDC field mapping solution documentation --------- Co-authored-by: root <chaowang1@alauda.io>
* Create ES_Scale_Switching.md * Update and rename ES_Scale_Switching.md to Elasticsearch_Scale_Switching.md * Update Elasticsearch_Scale_Switching.md * Update Elasticsearch_Scale_Switching.md
* add how-to-customize-consoleyamlsamples --------- Co-authored-by: huizhang <huizhang@alauda.io>
* add document for Label Studio Signed-off-by: tfwang <tfwang@alauda.io>
* add how to cleanup cluster image registry * add how to cleanup cluster image registry * add how to cleanup cluster image registry * add how to cleanup cluster image registry --------- Co-authored-by: huizhang <huizhang@alauda.io>
* support to deploy Milvus in ACP * add troubleshooting * refine doc * refine doc * refine doc * optimize docs * fix: Update Milvus examples to match tested E2E templates - Remove duplicate prerequisites section - Update standalone mode example to use tested rocksmq configuration - Update cluster mode example to use tested woodpecker configuration - Update GPU example to use tested cluster mode with indexNode/queryNode GPU allocation Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Jinpei Su <jpsu@alauda.io> Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* Add Langchain quickstart guide, notebook demo * update * update * update
* docs: 添加 OVN Underlay 首包延迟优化文档(S2 跳过 Conntrack 方案) * docs: 修复 review 反馈 - 中英文一致性和 YAML 上下文 - 删除中文版残留的 conntrack 表压力描述 - 补全 YAML 片段中 containers/name 定位信息 * docs: 用用户视角描述 skip conntrack 警告信息并修复中文术语 * docs: 修正 Service 警告描述 - 准确指向后端 Pod CIDR
Add StatefulSet application DR solution with VolSync. Signed-off-by: Xiaoxi He <xxhe@alauda.io>
workflow 里有 yarn set version stable — 自动拉最新 Yarn (现在是 4.14.1),超出 packageManager: yarn@4.13.0 pin,4.14 的 lockfile schema 升到 v9,immutable mode 拒绝迁移。 这不是我的 PR 引入的,是仓库 CI flake —— 自 2026-04-15 main 最后一次绿灯后,Yarn 4.14 发布就会触发。任何新 PR 都会中招。 修复最小化:workflow 里去掉 yarn set version stable,让 corepack 用 packageManager 字段固定的 yarn@4.13.0(跟仓库 lockfile v8 匹配)。提交到同一个 PR。
fd48a8d to
4b9c159
Compare
Summary
Summary by CodeRabbit