kubeovn/kube-ovn：README 來源編輯指南

kubeovn/kube-ovn 的 README 將專案描述為「A Bridge between SDN and Cloud Native (Project under CNCF)」。本文只整理倉庫可直接核對的內容，不把 star、Fork 或宣傳語當成品質證明。README 在「README」下寫到：Kube-OVN, a CNCF Sandbox Project, integrates OVN-based Network Virtualization with Kubernetes. It provides enhanced support for KubeVirt and unique Multi-Tenancy capabilities.。這說明的是專案邊界，不是已完成的生產驗證。

從 README 的「Features」與相關條目，可以先判斷它是否處理你的實際問題：Namespaced Subnets: Each Namespace can have a unique Subnet (backed by a Logical Switch). Pods within the Namespace will have IP addresses allocated from the Subnet. It's also possible for multiple Namespaces to share a Subnet.。若需求不同，不應只因專案熱度就採用。本文保留原始專案名、命令與元件名，方便回到一手來源核對。 README 另外列出一項可核對的資訊：VPC Support: Multi-tenant network with independent address spaces, where each tenant has its own network infrastructure such as eips, nat gateways, security groups and loadbalancers.。這類原文條目可用來設計試跑步驟，但不能取代實際環境測試。

README 將運作方式分散在「Community」等段落。可確認的線索包括：The Kube-OVN community is waiting for your participation!。本文不把未寫出的架構、效能或安全邊界補成結論；真正的執行鏈仍要配合目錄、設定檔與版本標籤檢查。

第一次安裝應從 README 指出的入口開始。目前可核對的命令是： README 没有给出可直接复制的安装命令。 如果倉庫沒有命令，本文不會自行編造步驟，而是建議先閱讀「Features」，確認系統依賴、預設埠與首次初始化。

日常使用取決於專案文件。README 的「Adopters」段落提到：A list of adopters and use cases can be found in USERS.md。設定檔、環境變數、權限與資料目錄只在來源明確時才會記錄；沒有寫出的預設值，應在測試環境驗證並保留回滾副本。 同一部分也提到：Vlan/Underlay Support: In addition to overlay network, Kube-OVN also supports underlay and vlan mode network for better performance and direct connectivity with physical network.。

README 能確認的限制比宣傳頁更重要。現有來源沒有證明kubeovn/kube-ovn具備固定相容矩陣、服務等級、效能基準或長期支援承諾。README 只明確寫到「Kube-OVN, a CNCF Sandbox Project, integrates OVN-based Network Virtualization with Kubernetes. It provides enhanced support for KubeVirt and unique Multi-Tenancy capabilities.」。這些未知項應列入選型紀錄，不要改成肯定句。