Dear all, I am writing to propose the creation of a separate apisix-go-sdk. Currently, the apisix-ingress-controller project contains logic related to operating the APISIX admin API. However, I believe that separating this logic into a standalone SDK would be beneficial for both users and the project itself.
With a separate apisix-go-sdk, users would be able to use it for independent development, or create their own terraform or pulumi provider using the SDK. This would allow for greater flexibility and customization of the use of APISIX admin API. In addition, separating this logic would also help reduce the maintenance cost of the apisix-ingress-controller project. By removing this functionality from the project, it can focus solely on its main goal of providing a Kubernetes ingress controller for APISIX. I believe that creating a separate apisix-go-sdk is a logical step forward for the apisix-ingress-controller project. It would allow for greater flexibility for users and a more streamlined focus for the project itself. I would love to hear your thoughts and feedback on this proposal. Please let me know if you have any questions or concerns. Thank you for your time and consideration. -- Best, Jintao Zhang GitHub: https://github.com/tao12345666333
