Exposing your APIs in the cluster
Fury Kong Addon
1 minute read
Our Kong module makes use of the official Kong ingress controller kustomize base manifests and extends it adding some Service Monitor and Rules.
The Fury Kubernetes Kong module can be deployed on the following platforms:
- AWS (no additional configuration required)
- Google Kubernetes Engine (GKE) - (no additional configuration required)
- Azure Kubernetes Service (AKS) - (no additional configuration required)
- on-premises or unmanaged cloud clusters (no additional configuration required)
The reference architecture used to deploy the Fury Kubernetes Kong Module is shown in the following figure:
The traffic from end users arrives to a Load Balancer that distributes the traffic between the available Kong Ingress Controllers (usually, one for each availability zone). Once the traffic reaches the Ingress Controller, the Ingress proxies the traffic to the service based on the URL and all Kong CRDs used to extend ingress functionality.
|kong||Kong ingress controller main package|
Was this page helpful?
Glad to hear it! Thanks for letting us know!
Sorry to hear that. Please tell us how we can improve.