-
Notifications
You must be signed in to change notification settings - Fork 594
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(*) refactor and simplify parsing of ingress rules to kong config
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
- Loading branch information
Showing
18 changed files
with
2,147 additions
and
2,793 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
227 changes: 4 additions & 223 deletions
227
internal/apis/configuration/v1/zz_generated.deepcopy.go
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.