2025-12-10 Eureka Gateway Update

2025-12-10 Eureka Gateway Update

Date

Nov 19, 2025 

 Join our Cloud HD Video Meeting  

Attendees 

TC members

  • @Julian Ladisch

  • @Olamide Kolawole

  • @Ingolf Kuss

  • @Florian Gleixner

  • @Christie Thomas

  • @Kevin Day

  • @Maccabee Levine

  • @Shelley Doljack

  • @Wayne Schneider

  • @Jeff Gerhard

  • @Jenn Colt

Guests

  • @Charlotte Whitt

  • @Craig McNally

  • @Matt Weaver

  • @Jason Root

  • @Raman Auramau

  • @VBar

  • @Viktor Gema

  • @Tod Olson

  • Stephan Pampell

  • @Jeremy Huff

  • Mahrad Zoonematkermani

  • Ranjith

Time

Item

Who

Notes

Time

Item

Who

Notes

1 min

Scribe

 

@Florian Gleixner followed by @Julian Ladisch

 

Reminder:  Please copy/paste the Zoom chat into the notes.  If you miss it, this is saved along with the meeting recording, but having it here has benefits.

 

https://folio-org.atlassian.net/wiki/x/AQDvUw

Craig

Craig:

As you may have already heard, Kong inc. decided earlier this year to stop contributing to, and building binary distributions of the open source version of Kong.  This kicked off an effort on the Eureka side to research our options going forward.  We've done this and would like to provide an update on our findings.  We'll walk you through our methodology and provide a summary of the findings.  In preparation for this discussion please take a look at the following documents, which are the artifacts coming out of the investigation/research.

@Craig McNally Key topics we looked at:

  • installation/deployment

  • costs / cost efficiency (hidden costs, infrastructure)

  • license stability

  • ecosystem stability

  • maturity

  • performance

  • compatibility

  • other things like: user interface, API

@Craig McNally goes through the Comparsion document. Additional comments were made:

@Viktor Gema APISIX does nor work with Postgres, but with etcd it works well.

@Viktor Gema Performance table: Numbers were taken from public sources. APISIX implemented Radix tree for routing, which will show better throughput and reduce memory consumption. Gloo uses 3-times memory.

@Viktor Gema Infrastructure: APISIX uses etcd, but if you run APISIX on kubernetes, it needs its own etcd

@Mark Veksler Which teams will have to care about the migration to a new gateway

@Craig McNally Not too many, most things will stay the same. The “application manager” will have to be adopted. Infrastructure teams will have to deploy the new Gateway including for example new variables and additional components like etcd. Sidecars may have to be adopted

@Jason Root Keycloak has some references to Kong

@Wayne Schneider Developers should create a deprecation policy for Kong related

@Wayne Schneider Is API stability for the control plane is included in the comparsion

@Viktor Gema All use standards like OpenAPI and jinx, should be stable

@Craig McNally Communication about changes is excellent in the blog of APISIX

@Shelley Doljack Does APISIX/Gloo change the versions rapidly and can we synchronize it with Flower releases

@Viktor Gema APISIX has frequent version changes, Gloo was not investigated

@Shelley Doljack Will the Folio community offer a Image for a new Gateway?

@Craig McNally Yes, we will create a image with a baseline configuration

@Jeremy Huff Will this be documented?

@Craig McNally Yes. Like with Kong GitHub - folio-org/folio-kong there will be a repository where you can lookup this

@Shelley Doljack Is nginx not going away?

Stephan Pampell, @Jason Root and others: It is just the Ingress Controller, that will go away, because Ingress API will get depricated. Gateway API is the replacement. Should not affect the nginx integration in the API Gateway.

@Kevin Day How will a decision affect the running or planned Eureka installations?

@Craig McNally Depends …

@Craig McNally Shall we decide via lazy consensus?

Stephan Pampell: We should think about costs and development time

@Shelley Doljack What are other open source projects doing? Are all Open Source Projects are moving from Kong to APISIX?

@Craig McNally and @Viktor Gema We have no insight here.

@Craig McNally We will come back here with a estimate about timing for development for moving to APISIX

@Mark Veksler Since the functionality is not changed by the switch to another gateway, should Eureka implementors wait for the switch or not?

@Craig McNally Hard to say

@Mark Veksler RMS group meeting is on monday, @Oleksii Petrenko will probably set then the Trillium GA date to late spring.

@Craig McNally Timing estimate before holidays great.

 

NA

Zoom Chat

 

2025-12-10 17:12:22 Von Mahrad Zoonematkermani Bis Alle:
please do highlight the important stuff :)

2025-12-10 17:20:29 Von Shelley Doljack Bis Alle:
Neat. Radix tree
Jason Root, Maccabee Levine:🆒

2025-12-10 17:29:08 Von Jason Root Bis Alle:
The same was done with Okapi WRT env var naming. 😬

2025-12-10 17:44:09 Von Viktor Gema Bis Alle:
F5 NGINX Gateway Fabric | NGINX Documentation

2025-12-10 17:47:36 Von Shelley Doljack Bis Alle:
Thanks all for clarifying that re: NGINX ingress controller.

2025-12-10 17:51:29 Von Wayne Schneider Bis Alle:
BRB

2025-12-10 17:54:37 Von Wayne Schneider Bis Alle:
Antwort auf „BRB“:
back

2025-12-10 17:58:28 Von Shelley Doljack Bis Alle:
I can’t hear him

2025-12-10 17:59:13 Von Jason Root Bis Alle:
I will add: Standing up etcd and best practices running it within infra WRT to the FOLIO stack will be something that will interest SysOps.

2025-12-10 17:59:24 Von Shelley Doljack Bis Alle:
Thanks again for the detail analysis and the evaluation matrices. 👏

2025-12-10 17:59:34 Von Wayne Schneider Bis Alle:
Timing is everything indeed. What are the chances that the APISIX release of the Eureka platform will align with Trillium GA?

2025-12-10 18:02:47 Von Mark Veksler Bis Alle:
thank you Craig and Viktor. Great work!

2025-12-10 18:03:12 Von Jason Root Bis Alle:
Cheers for all of the investigation on this migration.
Ingolf Kuss:👍