ronething commented on issue #2689: URL: https://github.com/apache/apisix-ingress-controller/issues/2689#issuecomment-3717279571
@jasaulakh1988 Hi, thank you for reporting this issue. ## Current Status We have attempted to reproduce this problem internally, but we are currently unable to reproduce the situation you described in our test environment. ref this test [PR](https://github.com/ronething/apisix-ingress-controller/pull/1). ## Additional Information Needed To help us better diagnose and reproduce this issue, please provide the following information: 1. **Kubernetes Version Information** - Please run `kubectl version` and provide the complete output - Include both client and server versions 2. **Detailed Reproduction Steps** - Detailed step-by-step instructions, it is necessary to include: - How to create the ApisixRoute resource, please provide the complete ApisixRoute YAML configuration ## Important Note It is important to note that **if there is only one backend in the ApisixRoute, the system will not generate separate upstream objects**. In this case, the upstream configuration will be directly inlined in the Service object. This is the current design behavior: - **Single backend**: Upstream is inlined in the Service (inline upstream) - **Multiple backends**: The first upstream is inlined in the Service, while other upstreams are created as separate objects and referenced via `upstream_id` This is also the reason why we are curious about your specific configuration. -- 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]
