You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: