Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[question] Centralized API Management #804

Open
pgillet opened this issue Feb 11, 2025 · 0 comments
Open

[question] Centralized API Management #804

pgillet opened this issue Feb 11, 2025 · 0 comments

Comments

@pgillet
Copy link

pgillet commented Feb 11, 2025

Maybe a stupid question, but I haven't found a straight answer anywhere.

Is it possible to deploy Apache APISIX in "decoupled" mode to allow centralized API management for APIs exposed in multiple Kubernetes clusters?

I know that centralized API management is already achievable with APISIX Ingress Controller which supports configuring external services as backends, with their direct domain, but this requires exposing these services externally, whereas we would like the API gateway service to be the only one exposed to the outside world.

I would like to deploy only one instance of the data plane (DP), i.e. a unique entry point, along with a centralized control plane (CCP) and deploy a control plane "agent" (CPA) per Kube cluster which would register to the CCP. Each agent would collect route/upstream configurations locally within its cluster to send them to the CCP.

The DP would redirect incoming requests to the right API in the right Kube cluster, via the CPA.

Am I messing around too much with the concepts here or is this something feasible?
If so, what would be the Helm configuration to achieve that?

Many thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant