Skip to content
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

Closed
1 of 4 tasks
randmonkey opened this issue Feb 27, 2023 · 5 comments
Assignees
Labels
area/feature New feature or request
Milestone

Comments

@randmonkey
Copy link
Contributor

randmonkey commented Feb 27, 2023

Is there an existing issue for this?

  • I have searched the existing issues

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

  • When gateway discovery is enabled, and kong gateway is DB-backed, KIC send kong configurations to only one of gateway clients.

Additional information

No response

Acceptance Criteria

  • When kong gateway is DB-backed, and KIC is configured to enable gateway discovery, KIC only sends configuration to one gatewat pod.
  • In the deployment above, all gateway nodes could receive the same configuration.
  • Have an "all-in-one-postgres-multiple-gw.yaml" that could deploy KIC with gateway discovery + kong with postgres DB backend
@mflendrich
Copy link
Contributor

Maybe we should instead disallow DB mode gateway if gateway discovery is enabled? (I believe we discussed that option on slack)

@pmalek
Copy link
Member

pmalek commented Feb 27, 2023

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.

@randmonkey
Copy link
Contributor Author

postpone this and do #3401 because we do not want to support gateway discovery with DB-backed gateways in KIC 2.9.

@mflendrich
Copy link
Contributor

Closing - we're supporting GD for DB-less only today.

@mflendrich mflendrich closed this as not planned Won't fix, can't repro, duplicate, stale May 8, 2023
@mheap
Copy link
Member

mheap commented Jun 7, 2023

@mflendrich Is there a replacement issue to support GD with DB-backed?

@randmonkey randmonkey reopened this Oct 12, 2023
@randmonkey randmonkey closed this as not planned Won't fix, can't repro, duplicate, stale Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/feature New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants