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

Feat/kong 1.0 to next #213

Merged
merged 4 commits into from
Dec 21, 2018
Merged

Feat/kong 1.0 to next #213

merged 4 commits into from
Dec 21, 2018

Conversation

hbagdi
Copy link
Member

@hbagdi hbagdi commented Dec 20, 2018

Introduce support for Kong 1.0

Breaking Change
---------------

Users wanting to benefit from projects like kube-lego can switch the
ingress class back to nginx.
As go-kong was bumped up for Kong 1.0, it introduces a few breaking API
changes.
@hbagdi hbagdi requested a review from fffonion December 20, 2018 20:37
@@ -148,7 +148,7 @@ func (n *NGINXController) syncGlobalPlugins() error {
// plugins in Kong
currentGlobalPlugins := make(map[string]kong.Plugin)
for _, plugin := range plugins {
if isEmpty(plugin.RouteID) && isEmpty(plugin.ServiceID) && isEmpty(plugin.ConsumerID) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this and the following several changes needed because the api change in the upstream go-kong library?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, which was needed because Kong 1.0

@hbagdi hbagdi merged commit 3a0a4e3 into next Dec 21, 2018
@hbagdi hbagdi deleted the feat/kong-1.0-to-next branch December 21, 2018 00:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants