You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now I have paused the project, because Kong has released their GUI Kong Manager with the OpenSource version of Kong (OSS), so i'm thinking about if it is worth continuing with it or not.
The main difference between Kong Manager and King is the Architect interface (the graph mode), that makes more visual the management of kong elements. Maybe King is a little bit more usable than Kong Manager too. But hey are improving this last point with each release, e.g. in the last release they have included a wizard to aid in the route expression creation.
So, my point is, is it worth the effort of maintining King only for the graph interface? I'm not sure, and just taking some time watching if they improve Kong Manager's usability more so that King is not necesary anymore.
All that said, maybe if I have some time soon I'll update Angular and review Kings compatiblity with last Kong version once more. Hope Angular does not give a lot of problems... sometimes its hard to upgrade it.
@thangaraja Have you detected any compatibility problems with latest versions of Kong I must be aware of?
Hi,
Is there a plan to upgrade to Angular 18 along with the support for latest version of Kong?
The text was updated successfully, but these errors were encountered: