๐Ÿ“ฆ XVincentX / express-gateway-ingress-controller

A Kubernetes ingress controller driven by Express Gateway

โ˜… 3 stars โ‘‚ 0 forks ๐Ÿ‘ 3 watching
๐Ÿ“ฅ Clone https://github.com/XVincentX/express-gateway-ingress-controller.git
HTTPS git clone https://github.com/XVincentX/express-gateway-ingress-controller.git
SSH git clone git@github.com:XVincentX/express-gateway-ingress-controller.git
CLI gh repo clone XVincentX/express-gateway-ingress-controller
Vincenzo Chianese Vincenzo Chianese Add readme e049c4b 7 years ago ๐Ÿ“ History
๐Ÿ“‚ master View all commits โ†’
๐Ÿ“„ .dockerignore
๐Ÿ“„ .gitignore
๐Ÿ“„ Dockerfile
๐Ÿ“„ eg-client.js
๐Ÿ“„ index.js
๐Ÿ“„ ingress.yaml
๐Ÿ“„ package-lock.json
๐Ÿ“„ package.json
๐Ÿ“„ README.md
๐Ÿ“„ skaffold.yaml
๐Ÿ“„ README.md

eg-ingress-controller

This is a WIP experiment to use Express Gateway as an Ingress Controller for Kubernetes

In the case it'll reach a production/decent state, I'll finish the Readme.

Express Gateway limitations

  • Express Gateway has a serious concurrency problem using the WebAPI. Given the configuration is stored on file,
if two calls happen at the same time using the Admin API, they'll really likey result in an invalid config file.

  • Express Gateway does not support a way to add to modify the SNI list at runtime. Once it's started, the array can't
be changed.