Related functions are ready, and in this PR I also corrected all e2e use cases. PTAL
https://github.com/apache/apisix-ingress-controller/pull/698 Jintao Zhang <[email protected]> 于2021年10月1日周五 下午11:28写道： > PR is here: > https://github.com/apache/apisix-ingress-controller/pull/698 > > > Chao Zhang <[email protected]> 于2021年9月26日周日 下午7:12写道： > >> +1, but are there other fields can be deprecated together? >> >> Chao Zhang >> https://github.com/tokers >> >> On September 26, 2021 at 10:32:04, Jintao Zhang ( >> [email protected]) wrote: >> >> In the current ApisixRoute CRD definition, there are both `spec.backend` >> and `spec.backends` [1] >> >> And `spec.backends` can completely cover the usage scenarios of >> `spec.backend`. Currently maintaining these two fields at the same time >> has caused a certain burden on us. >> For example, when the resource cannot be obtained directly through >> kubectl, >> the corresponding information can be displayed. For details, please see >> >> https://github.com/apache/apisix-ingress-controller/pull/626#discussion_r686714645 >> >> **I suggest that we upgrade ApisixRoute to v2beta2 version as soon as >> possible, and deprecate `spec.backend` in this version.** >> >> [1]: >> >> https://github.com/apache/apisix-ingress-controller/blob/957c31522e1b1e5f8ef9cab7eb244473a4e0f675/samples/deploy/crd/v1beta1/ApisixRoute.yaml#L173-L217 >> >> >> >> >> ---- >> Jintao Zhang >> Twitter: https://twitter.com/zhangjintao9020 >> >>
