-
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
Support multiple gateways connected to different databases #4845
Comments
Does this indeed follow from #4751? AFAIK we've never supported the notion of a single Kong cluster where some instances use one database and others another. DB HA considerations are handled at the DB level, with replica configuration opaque behind a single DB hostname for all Kong instances. There was some discussion in the distant past re a single controller instance managing separate Kong clusters, but that was in the context of automatically provisioning clusters for multiple incompatible Gateways and sending each its appropriate configuration. I don't think that's what this is trying to tackle, since it's implying the same configuration to both databases. |
Is there an existing issue for this?
Problem Statement
Following of #4751. If the Kong admin API service is pointing to a set of Kong pods backed by different databases (different host/port/DB name), KIC needs to choose one client connected to each different DB to keep every instance synced with the latest configuration.
Proposed Solution
/configuration
admin API endpoint and group clients by the DB ("local" host in different instances should be considered as different hosts)Additional information
No response
Acceptance Criteria
The text was updated successfully, but these errors were encountered: