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.

Sign up for GitHub

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

Jump to bottom

bug: Global plugins are not treated same as other plugins #502

Closed
hbagdi opened this issue Jan 13, 2020 · 0 comments · Fixed by #516
Closed

bug: Global plugins are not treated same as other plugins #502

hbagdi opened this issue Jan 13, 2020 · 0 comments · Fixed by #516

Comments

@hbagdi
Copy link
Member

hbagdi commented Jan 13, 2020

Summary

Properties like protocols and other properties don't take any effect

Kong Ingress controller version

0.7.0

Kong or Kong Enterprise version

1.14

Kubernetes version

1.15

What happened

Plugins labeled with the global do not reflect a change in protocols field.
hbagdi added a commit that referenced this issue Jan 22, 2020
@hbagdi
fix(parser) global plugins are processed same as regular ones
bc73ece 
Protocols, Enabled and other fields are processed for global plugins as
well. This was ignored previously.

Fix #502
@hbagdi hbagdi mentioned this issue Jan 22, 2020
Merged
hbagdi added a commit that referenced this issue Jan 27, 2020
@hbagdi
fix(parser) global plugins are processed same as regular ones
a0c373e 
Protocols, Enabled and other fields are processed for global plugins as
well. This was ignored previously.

Fix #502
From #516
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(parser) global plugins are processed same as regular ones Kong/kubernetes-ingress-controller
1 participant
@hbagdi