mfordjody opened a new issue, #826: URL: https://github.com/apache/dubbo-go-pixiu/issues/826
### ✅ 验证清单 - [x] 🔍 我已经搜索过 [现有 Issues](https://github.com/apache/dubbo-go-pixiu/issues)，确信这不是重复问题 ### ✨ 提案摘要 In the previous controller design, we used both Ingress and Gateway API resource objects and watched for their changes, supporting interfaces such as proxy. In the latest design, the Ingress resource objects and proxy interfaces have been removed. Only Gateway API resource objects are supported. The reason is that Ingress resources have limited functionality and make future extensibility difficult. ### 🛠️ 实现方法 Therefore, a translator and a converter have been added. The translator can convert standard Gateway API resources into an implementation-agnostic IR xDS. Using IR xDS allows unified management of all types of listeners. However, this xDS can be considered static xDS, because in Pixiu the conf.yaml belongs to static_resources, meaning it is not a dynamic configuration protocol. The converter also uses ConfigMap, so if dynamic resources were required, the ConfigMap would need to be replaced with an actual xDS server. The converter transforms the standardized IR xDS into a configuration format that Pixiu can understand and execute, which is the content of conf.yaml. <img width="362" height="474" alt="Image" src="https://github.com/user-attachments/assets/1edd890a-89c1-4e12-a1da-50ea66af20bd"; /> When we create a Gateway, the built-in Pixiu Gateway resource automatically creates two objects: a Pixiu Gateway Deployment and a LoadBalancer Service. After these are created, the process continues through the conf.yaml ConfigMap, and finally the Pixiu Gateway is fully created. <img width="256" height="642" alt="Image" src="https://github.com/user-attachments/assets/e8a13ee3-e22d-4f28-b7e0-13a226b47f3f"; /> ### 📚 附加上下文 _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
