This is the second instalment of “Learning API Gateways” series. In the last episode, we learnt about the Tyk Api Gateway. Below I’m leaving behind some of the relevant links; do checkout these, if you haven’t yet!
Industry landscape of Api Gateways — https://sanjimoh.medium.com/api-gateway-landscape-347b91639f0b
A walkthrough of Tyk Api Gateway — https://dev.to/sanjitun/tyk-api-gateway-a-walkthrough-1npp
My focus has been around Kubernetes platform & how each of the industry API Gateways natively support it.
In today’s episode of Learning API Gateway series, I’ll take you through — Apache Apisix Api Gateway. You can find the video of this episode in the bottom of this article.
Hope you all find it useful!
Note :- Support for Kubernetes Gateway Api exists in Apache Apisix; however there are some caveats -
I felt its documentations could be organised better to make it more accessible; especially finding notes around its support for Kubernetes Gateway API wasn’t really an easy task. You need to install Apisix in a specific way to enable it’s support for Kubernetes Gateway API & this wasn’t very obvious for me to start with.
With the current Apisix SW version, deletion of Kubernetes Gateway httproutes resource doesn’t delete the corresponding Apisix route configurations. I created a GitHub ticket for the same and learnt that this feature is going to be available with the newer version of Apisix (1.5.0) which is yet to be released.
Top comments (0)