-
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
Rewrite translation of Ingress spec to Kong resources #241
Labels
work in progress
Work In Progress
Comments
This was referenced Mar 8, 2019
hbagdi
added a commit
that referenced
this issue
Apr 1, 2019
Breaking changes - KongIngress overrides for Service and Upstream will now be picked up from annotation on the service and not the route. Changelog: - Directly translate to Kong configuration objects Previously, the Ingress rules were parsed into Nginx Server and Location blocks, and then translated to Kong configuration. This was more complicated and information was lost during translation. - Translation is now done to an intermediate Kong state and then further translated to the final format. The final format will differ, based on if Kong is running in a db or a db-less mode. - Method based routes are now supported (#202) - Default backend in Ingress rules is now respected and a default fallback route in Kong will be created if a default backend exists in one of the Ingress objects. If multiple Ingress objects have a default backed, the Ingress created first will be respected. Fix #202 Fix #241
Is this issue released ? since I can see the corresponding PR is already closed |
@eshepelyuk 0.4.0 release coming up soon (a few days) which will include these changes. |
@eshepelyuk Yes, the support for it is already landed in |
Thanks for reply, will wait until features will be closed :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Currently, Ingress Controller takes in all the Ingress rules and translates them into Server and Location blocks, very similar to how Nginx is configured. This is the case because this controller was forked from the nginx ingress controller and then updated to get it to work with Kong.
This results in a few problem
Solution
Translate Ingress rules, along with associated KongIngress objects directly into Kong resources.
This can capture all Kong specific configuration properties and leverage Kong's declarative configuration capabilities.
The text was updated successfully, but these errors were encountered: