是否可以用apisix作为k8s集群内部的服务的api-gateway

[andyzheung]

Description

由于k8s集群内部的服务之间也会相互调用，但是希望能够统一将限流、鉴权等做到一起，因此希望所有集群内部的后端服务互访也通过一个gateway进行。 但是看了apisix的gateway只支持nodeport和lb模式，不知道是否能够支持我说的这种需求。 集群内服务互访不走coredns域名，都走到api-gateway，然后再转到后端。

Environment

1、k8s环境。

[tzssangglass]

You mean using APISIX to proxy east-west traffic?

cc @tokers @tao12345666333

[tzssangglass]

I think this would help for you: https://github.com/apache/apisix/blob/master/docs/en/latest/discovery/kubernetes.md

[tao12345666333]

sure, its a basic function

[andyzheung]

APISIX to proxy east-west traffic?

是的，希望用gateway解决集群内部的东西向流量，不用绕到外部。

[andyzheung]

I think this would help for you: https://github.com/apache/apisix/blob/master/docs/en/latest/discovery/kubernetes.md

看了这篇文章，但并不理解如何配置k8s集群内部的微服务如何通过apisix来作为网关。

[tzssangglass]

看了这篇文章，但并不理解如何配置k8s集群内部的微服务如何通过apisix来作为网关。

We can't fix that you don't understand something. You can come to us with a specific problem and ask for help.

[tokers]

Yes, this doc shows how you can configure the Kubernetes service discovery on APISIX. As for how other components can call APISIX, it varies and depends on your topology and business needs.

[github-actions[bot]]

This issue has been marked as stale due to 350 days of inactivity. It will be closed in 2 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the [email protected] list. Thank you for your contributions.

[github-actions[bot]]

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.