gxthrj opened a new issue #120: URL: https://github.com/apache/apisix-ingress-controller/issues/120
During the development process, we maintained some additional complexity, because of splitting the CRD (custom resource object) to `ApisixRoute` `ApisixService` and `ApisixUpstream`. Controller need to handle broken links between resources and/or mismatched configuration. I proposal combine `ApisixRoute`, `ApisixService`, `ApisixUpstream` into one resource object `ApisixRoute`. Benefits: Using a single resource object to define routing rules will effectively reduce the maintenance cost of internal relationships. Downsides: There will be more configuration items and the internal structure of `ApisixRoute` will become bloated. There are two solutions for the processing of `ApisixRoute` and `ApisixService`: 1. Keep them Continue to keep `ApisixService` and `ApisixUpstream` as supplementary configuration to `ApisixRoute`, but the routing configuration will not fail due to the failure of `ApisixService` and `ApisixUpstream`. 2. Ignore it, configuration no longer takes effect. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
