With the help of this tool, we can also optimize the config snippet in the document, i.e. providing different configuration types (Restful, Declarative Configurations)
Chao Zhang https://github.com/tokers On December 28, 2021 at 11:51:28, Jintao Zhang (zhangjintao9...@gmail.com) wrote: HI, folks Consider the following scenario: Current users are already using Apache APISIX as the Gateway. With the popularity of Cloud Native, users want to migrate to the Kubernetes environment. The best way to use Apache APISIX in a Kubernetes environment is to use the APISIX Ingress controller. Users need to be migrated. If we can provide a tool to convert existing resources such as routes/upstreams in Apache APISIX into custom resources of APISIX Ingress controller, it will be very convenient. At present, we have implemented the APISIX client in the APISIX Ingress controller, as well as the definition of its resource structure[1] And the data structure of the custom resource in the APISIX Ingress controller[2] So this tool only needs: Initialize APISIX client -> Fetch routes/upstreams resources -> Structure translation[3] -> Output manifest file [1]: https://github.com/apache/apisix-ingress-controller/blob/master/pkg/types/apisix/v1/types.go [2]: https://github.com/apache/apisix-ingress-controller/blob/master/pkg/kube/apisix/apis/config/v2beta3/types.go [3]: https://github.com/apache/apisix-ingress-controller/tree/master/pkg/kube/translation --- Best, Jintao Zhang
