Kong
The event-hook delete operation cannot be automatically synchronized across multiple Kong instances.
Is there an existing issue for this?
- [x] I have searched the existing issues
Kong version ($ kong version)
kong 3.10
Current Behavior
Multiple Kong instances with one database. When an event-hook is created or deleted on one Kong instance, the event-hook is not automatically synchronized and deleted on the other nodes. The changes only take effect on those nodes after they are restarted.
Expected Behavior
No response
Steps To Reproduce
No response
Anything else?
No response
Could you give me a practical example — in what situation you used it, whether in a plugin or in some modified Kong code? Or, alternatively, could you share steps to reproduce it?
Could you give me a practical example — in what situation you used it, whether in a plugin or in some modified Kong code? Or, alternatively, could you share steps to reproduce it?
A and B are both connected to the same database. Steps to reproduce the issue:
Use A's admin API to create an eventhook for the target, then use B's admin API to create a target; the eventhook is triggered as expected. Use A's admin API to delete this eventhook, then use B's admin API to create a target; the eventhook has not been deleted and can still be triggered.
The event-hook relies on worker events to update, which are triggered by the config sync or Admin API. This is not handled in the case of multiple nodes sharing the same DB. Other nodes are not aware of the change, unless notified with a cluster event. The hybrid mode is encouraged in this use case
This issue is marked as stale because it has been open for 14 days with no activity.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Dear contributor,
We are automatically closing this issue because it has not seen any activity for three weeks. We're sorry that your issue could not be resolved. If any new information comes up that could help resolving it, please feel free to reopen it.
Your contribution is greatly appreciated!
Please have a look our pledge to the community for more information.
Sincerely, Your Kong Gateway team