Skip to content

Latest commit

 

History

History
42 lines (30 loc) · 2.67 KB

README.md

File metadata and controls

42 lines (30 loc) · 2.67 KB

Kong

Kong is an open-source API gateway that is built on top of a lightweight proxy, Nginx.

Troubleshooting

Kong doesn't support ARM7

You can find the issue here. I was trying to compile it on ARM7 but I was wasting so much time and I wasn't getting any results.

Because of that and because Kong support now ARM64. I upgraded one of my RPi to a 64 Bit Kernel following this article.

I used Kubernetes Node affinity to define my RPI node as a special node with arm64 arch and I updated my k8s template to only work in this kind of RPI Node.

I found that the Kong image was built on linux/arm64/v8 and my stack was requiring linux/arm64. I built my own version ymedlop/kong:2.0.1-ubuntu.

About the ingress-controler image. I used leandrocarneiro/kong-ingress-controller:0.7.0.

Konga doesn't support ARM64

Konga is a GUI to Kong Admin API with these features:

  • Manage all Kong Admin API Objects.
  • Import Consumers from remote sources (Databases, files, APIs etc.).
  • Manage multiple Kong Nodes.
  • Backup, restore and migrate Kong Nodes using Snapshots.
  • Monitor Node and API states using health checks.
  • Email & Slack notifications.
  • Multiple users.
  • Easy database integration (MySQL, postgresSQL, MongoDB).

Github issue about ARM64 because of that I am working on my own image with ARM64 support.

Exposing Api Gateway on Private Kubernetes Clusters with a Public IP

We going to use inlets-operator. It automates the creation of an inlets exit-node on public cloud, and runs the client as a Pod inside your cluster. Your Kubernetes Service will be updated with the public IP of the exit-node and you can start receiving incoming traffic immediately.

The cost of the LoadBalancer with a IaaS like DigitalOcean is around 5 USD / mo.

Deploy Kong in our Cluster

PAASMONKEYS