-
Notifications
You must be signed in to change notification settings - Fork 591
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When Gateway discovery is enabled and Kong is DB backed, KIC only sends config to one of Kong gateway endpoint #3606
Comments
Maybe we should instead disallow DB mode gateway if gateway discovery is enabled? (I believe we discussed that option on slack) |
I agree that we could do this for 2.9 (as initially intended in #3401). We can then expand in 2.10 (or later). That would be IMHO the best course of action, rather than trying to ship everything at once (and have a bigger surface for potential bugs). OTOH if we intend to deliver this then #3401 should be closed as not planned. |
postpone this and do #3401 because we do not want to support gateway discovery with DB-backed gateways in KIC 2.9. |
Closing - we're supporting GD for DB-less only today. |
@mflendrich Is there a replacement issue to support GD with DB-backed? |
Is there an existing issue for this?
Problem Statement
In DB-backed deployment of kong gateway, KIC should only send to one of gateway admin API endpoints, and kong gateway instances could do the synchronization of configuration via DB. So, instead of limiting gateway discvoery/SCD to be used with only DB-less mode (#3401), we could let KIC to send configuration on any one of available gateway clients when gateway discovery is enabled, to enable KIC to work with multiple DB-backed gateway instances.
Proposed Solution
Additional information
No response
Acceptance Criteria
The text was updated successfully, but these errors were encountered: