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

Add support for Consumer only plugins #250

Closed
hbagdi opened this issue Mar 20, 2019 · 3 comments
Closed

Add support for Consumer only plugins #250

hbagdi opened this issue Mar 20, 2019 · 3 comments
Milestone

Comments

@hbagdi
Copy link
Member

hbagdi commented Mar 20, 2019

Currently, plugins can be defined on route level, service level or a combination of route+consumer and service+consumer.

The controller should be able to configure consumer-only plugin.

@hbagdi hbagdi added this to the 0.5.0 milestone Jun 7, 2019
hbagdi added a commit to hbagdi/kubernetes-ingress-controller that referenced this issue Jun 7, 2019
Consumer level plugins can be configured using plugins.konghq.com
annotation on the KongConsumer resource.

See Kong#250
hbagdi added a commit that referenced this issue Jun 7, 2019
Consumer level plugins can be configured using plugins.konghq.com
annotation on the KongConsumer resource.

See #250
From #306
@hbagdi
Copy link
Member Author

hbagdi commented Jun 7, 2019

Added with #306 and will be available with Kong Ingress Controller 0.5.0, set to be released mid June.

@hbagdi hbagdi closed this as completed Jun 7, 2019
@WoodyFleurant
Copy link

WoodyFleurant commented Oct 27, 2019

@hbagdi if I understand correctly it's not possible right now to have
plugins.konghq.com: key-auth,acl-group on kind: Ingress?

@hbagdi
Copy link
Member Author

hbagdi commented Oct 28, 2019

No, it is possible to do that.

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

No branches or pull requests

2 participants